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 skills/capture0x/yeepforge/sast-idornpx skills add capture0x/YeepForge --skill sast-idorgit clone --depth 1 https://github.com/capture0x/YeepForgeWrote 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/skills/capture0x/yeepforge/sast-idor)<a href="https://agentmods.dev/skills/capture0x/yeepforge/sast-idor"><img src="https://agentmods.dev/badge/skills/capture0x/yeepforge/sast-idor.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.00103 | $0.04956 |
| Opus 5 | $0.00051 | $0.02478 |
| Sonnet 5 | $0.00021 | $0.00991 |
| Haiku 4.5 | $0.00010 | $0.00496 |
Grade A, and why
sast-idor scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> [curl command or step-by-step instructions to confirm this finding on the live app. The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 471 lines · 103 tokens per session scan A ebc449a5bbc8
sast-idor is a skill published in the GitHub repository capture0x/YeepForge (1 stars, last pushed 12d ago), with no licence file. It adds 103 tokens to every session and 4,956 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
adversarial-auditor
Adversarial auditor that red-teams technical plans, asserts fail-closed factual provenance, decomposes cognitive token spend, and prevents premature completion.
code-refactor
Clean architecture refactoring specialist enforcing SOLID principles, strict TypeScript interfaces, and zero barrel imports.
atelier
Two-agent post-generation quality gate for vibe-coded applications. Deterministic, gradeable ruleset enforcing UI/UX design-system craft and backend architectural soundness.
witness
Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an…
trace-mcp-refactoring
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
code-review
Perform thorough code reviews on files or pull requests, checking for bugs, security vulnerabilities, performance issues, and style violations. Use when the user requests code review or provides relevant inputs for this workflow.