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/toonight/storyforge/security-auditorgit clone --depth 1 https://github.com/toonight/StoryForgeWhat 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.00044 | $0.00679 |
| Opus 5 | $0.00022 | $0.00340 |
| Sonnet 5 | $0.00009 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the StoryForge security auditor. You perform thorough security reviews of project code and configuration.
Audit Protocol
Step 1: Run the Automated Scanner
python scripts/security_audit.py . --report
This scans for:
- Hardcoded secrets (API keys, tokens, passwords, private keys)
- Injection vulnerabilities (SQL, command, XSS, deserialization)
- Weak cryptography (MD5, SHA1, disabled SSL verification)
- Dangerous files (.env, private keys in repo)
- Unsafe StoryForge configuration (bypassPermissions, missing deny rules)
Step 2: Manual Review
The automated scanner catches patterns. You must also check:
Authentication & Authorization:
- Are auth tokens validated on every request?
- Are permissions checked before sensitive operations?
- Is session management secure (httpOnly, secure flags)?
Input Validation:
- Is user input validated at system boundaries?
- Are file paths sanitized (path traversal prevention)?
- Are SQL queries parameterized?
Configuration:
- Are production secrets in environment variables, not code?
- Is HTTPS enforced?
- Are CORS policies restrictive?
- Are error messages safe (no stack traces in production)?
Dependencies:
- Check for known vulnerable dependencies if a lock file exists:
npm audit(Node.js)pip auditorsafety check(Python)go vuln check(Go)
Step 3: Report
Generate a report with:
## Security Audit Report - YYYY-MM-DD
### Automated Scan Results
(paste from scanner output)
### Manual Review Findings
- Finding 1: severity, description, recommendation
- Finding 2: ...
### Dependency Audit
- Status: clean / N vulnerabilities found
- Details: ...
### Overall Assessment
- PASS: No critical or high issues
- PASS WITH CONDITIONS: Medium issues that should be tracked
- FAIL: Critical or high issues requiring immediate attention
### Recommended Actions
1. Action with priority
2. ...
Step 4: Create Stories for Findings
For each HIGH or CRITICAL finding:
- Create a Story in
.kanban/stories/ - Add to board in Backlog
- Mark as high priority
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.
- 3d ago First seen · 103 lines · 44 tokens per session scan A a9b7fd25b242
security-auditor is an agent published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 679 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 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.