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/starter-series/create-starter/seed-security-guidancegit clone --depth 1 https://github.com/starter-series/create-starterWrote 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/starter-series/create-starter/seed-security-guidance)<a href="https://agentmods.dev/commands/starter-series/create-starter/seed-security-guidance"><img src="https://agentmods.dev/badge/commands/starter-series/create-starter/seed-security-guidance.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.1 | $0.00048 | $0.00522 |
| Opus 5 | $0.00024 | $0.00261 |
| Sonnet 5 | $0.00010 | $0.00104 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
seed-security-guidance 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 5d 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
You are seeding a starter claude-security-guidance.md so Anthropic's Claude Code Security Guidance Plugin can use it as an in-session guard while writing code.
Steps
-
Call the
seed_security_guidanceMCP tool withpathset to the absolute path of the repo. If no path is given, use the MCP server's cwd. Passforce: trueonly when the user explicitly asks to overwrite an existing file. -
Surface the report:
- status —
created(new file),exists(file present, no change), oroverwritten(file was replaced becauseforce: true). - matched starter — which Starter Series template informed the starter-specific section.
nullmeans the generic fallback section was used. - relative path — where the file landed (always
claude-security-guidance.mdat repo root for now).
- status —
-
If
status === "exists", tell the user the file is already in place; offer to re-run with--forceonly if they want the latest template. -
If
status === "created" | "overwritten", suggest:- Read the generated file and edit any org-specific rules in the marked sections.
- Commit via
git add claude-security-guidance.md && git commit -m "chore(security): seed claude-security-guidance.md". - Re-run
audit_securityto confirm theclaude-security-guidancecheck flips to PRESENT.
Positioning
This complements (does not replace):
claude-code-security-reviewGitHub Action — runs on every PR, AI review of diffs.audit_securityMCP tool — detects this file's presence as the 9th check.
The three together: in-session guard (this), post-PR review (claude-code-security-review), repo-level static audit (audit_security).
Do NOT
- Pass
force: truewithout explicit user confirmation — it overwrites any hand-edited rules. - Edit the file's content yourself from this command. Generate it via the MCP tool, then let the user edit.
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.
- 5d ago First seen · 36 lines · 48 tokens per session scan A 633f6c0e6d76
seed-security-guidance is a command published in the GitHub repository starter-series/create-starter (2 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 522 once invoked, about $0.0002 per session on Opus 5. 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-31.
Other commands, from other repositories
verify
Fidelity check — rebuild a page from the extracted tokens, pixel-diff it against the live site, and score how faithfully the tokens capture the design.
battle
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.
cli-anything-web:list
List all available CLI-Anything-Web CLIs (installed and generated).
zh
切换 Claude Code 为简体中文（/chinese 的短别名）.
note
Add a note to the active task - progress, decisions, context. --session (aliases --snapshot, --pre-compact, --compact) writes a resume-grade session snapshot without ending the session.
restaurant-snipe
Schedule a future reservation to book at the exact release time (e.g. 10am sharp when Resy slots open).