What does the Security — vulnerability disclosure policy prompt produce?

A security website with Policy hero, Scope table, Response commitments, Safe harbour. The vibe target is "technical, plain, non-defensive" and the prompt body is printed in full on the page.

How well does it score?

89% average fidelity over 3 recorded runs. Best model: Claude 4.6 Sonnet. Weakest recorded run: 87% on Codex.

Are failures included?

No build failures are recorded for this prompt, and the log says so rather than implying every model succeeded elsewhere.

Concept render — composed live from this prompt's palette & layout. Reproducible with the library, not a stock screenshot.

Concept scene: Liquid Glass — open in library →

SecurityVerifiedby Motif Studiopublished 2026-09-17

Security — vulnerability disclosure policy

vibe: technical, plain, non-defensive

starter — 4 blocks, 2 stacksany viewport≈ 260 lines generated (estimate)≈ 600 tokens to run (estimate)

prompt.txt — copy-paste ready

A vulnerability disclosure policy page: a hero giving the reporting address and response window up front, a scope table naming what is in scope and what is not (third-party services, social engineering, physical access), response commitments as a numbered list of what the team will do and by when, and a safe-harbour section stating what the organisation will not do to a good-faith researcher — no "we take security seriously", no bounty figures without a bounty. Ink on cool paper, one accent. Scope rows carry a hover state; colours are CSS variable tokens; reduced-motion keeps the page still.

Palette tokens:#f4f6f8#262016#3a6b5a#5a6472

Remix this brief: