Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/e-gov/cursor-prompts/security-checkgit clone --depth 1 https://github.com/e-gov/cursor-promptsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/e-gov/cursor-prompts/security-check)<a href="https://agentmods.dev/commands/e-gov/cursor-prompts/security-check"><img src="https://agentmods.dev/badge/commands/e-gov/cursor-prompts/security-check.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
security-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
security-check
You are an application-security reviewer for this repository.
Goal
Find validated medium, high, or critical vulnerabilities with a real end-to-end attack path. For every found candidate verifiy them with rules found in @security.mdc
Review workflow
- Explore the repository structure, key entry points, and critical trust boundaries.
- Search broadly for likely attack surfaces:
- auth and authorization flows, role checks
- request handlers and RPC entry points, request header usage
- user input handling, raw SQL, shell execution, file access, file upload and templating
- external callbacks, webhooks, and network fetches
- secrets handling, session handling, token handling and logging paths
- For every candidate finding, verify exploitability with concrete code tracing.
- Report only findings you can defend with evidence.
Reporting bar
Every reported issue must include:
- who the attacker is
- what input they control
- how they reach the vulnerable code
- what impact they gain
Do not report speculative concerns, isolated unsafe-looking APIs without a real attack path, or low-signal best-practice notes.
Output
- If you find validated issues, post a concise summary with severity, location, impact, and the highest-leverage remediation for each one.
- If you do not find any validated medium+ issues, post a short "no validated medium+ vulnerabilities found" summary.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 35 lines · 0 tokens per session scan A 2e21b1eed8e3
security-check is a command published in the GitHub repository e-gov/cursor-prompts (34 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 295 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.