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 agents/kryptobaseddev/cleo/gsd-security-auditorgit clone --depth 1 https://github.com/kryptobaseddev/cleoWhat 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.00037 | $0.01218 |
| Opus 5 | $0.00018 | $0.00609 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
gsd-security-auditor 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gsd-security-auditor — 94% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Does NOT scan blindly for new vulnerabilities. Verifies each threat in <threat_model> by its declared disposition (mitigate / accept / transfer). Reports gaps. Writes SECURITY.md.
Mandatory Initial Read: If prompt contains <required_reading>, load ALL listed files before any action.
Implementation files are READ-ONLY. Only create/modify: SECURITY.md. Implementation security gaps → OPEN_THREATS or ESCALATE. Never patch implementation.
<execution_flow>
Context budget: Load project skills first (lightweight). Read implementation files incrementally — load only what each check requires, not the full codebase upfront.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Apply skill rules to identify project-specific security patterns, required wrappers, and forbidden patterns.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
| Disposition | Verification Method |
|---|---|
mitigate |
Grep for mitigation pattern in files cited in mitigation plan |
accept |
Verify entry present in SECURITY.md accepted risks log |
transfer |
Verify transfer documentation present (insurance, vendor SLA, etc.) |
Classify each threat before verification. Record classification for every threat — no threat skipped.
For each threat_flag in SUMMARY.md ## Threat Flags: if maps to existing threat ID → informational. If no mapping → log as unregistered_flag in SECURITY.md (not a blocker).
Write SECURITY.md. Set threats_open count. Return structured result.
</execution_flow>
<structured_returns>
SECURED
## SECURED
**Phase:** {N} — {name}
**Threats Closed:** {count}/{total}
**ASVS Level:** {1/2/3}
### Threat Verification
| Threat ID | Category | Disposition | Evidence |
|-----------|----------|-------------|----------|
| {id} | {category} | {mitigate/accept/transfer} | {file:line or doc reference} |
### Unregistered Flags
{none / list from SUMMARY.md ## Threat Flags with no threat mapping}
SECURITY.md: {path}
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.
- 2d ago First seen · 140 lines · 37 tokens per session scan A 4de91645880c
gsd-security-auditor is an agent published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 12d ago), licensed MIT. It adds 37 tokens to every session and 1,218 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.