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/aneja5/forge-skills/validategit clone --depth 1 https://github.com/aneja5/forge-skillsWhat 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.00013 | $0.00175 |
| Opus 5 | $0.00006 | $0.00088 |
| Sonnet 5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
validate 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.
What it actually says
Invoke the forge-skills:cross-validation skill.
Two-phase flow:
Phase 1 (no .forge/cross-validation-prompt.md exists): Read available .forge/ artifacts. Compile self-contained context that a reviewer can assess without prior knowledge. Write 10+ specific questions across architecture, security, scalability, business model, and risk categories. Output: .forge/cross-validation-prompt.md Tell user: "Send this to your reviewers. Run /validate again with responses."
Phase 2 (.forge/cross-validation-prompt.md exists and user provides responses): Synthesize responses into consensus levels (unanimous, strong, split, dissent). Extract actionable changes (must / should / monitor). Output: .forge/cross-validation-synthesis.md
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 · 20 lines · 13 tokens per session scan A 83c244b3a8b6
validate is a command published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 175 once invoked, about $0.0001 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
index
Command "index" from cesarandreslopez/tauri-agent-tools, covering command reference, command summary, categories, visual capture and dom inspection.
snapshot
Capture screenshot + DOM tree + page state + storage in one shot.
storage
Inspect localStorage, sessionStorage, and cookies from the Tauri webview. One-shot read — no writes.
eval
Evaluate a JavaScript expression in the Tauri app's webview.
list-windows
List all visible windows, marking Tauri apps.
audit
Framework setup and infrastructure compliance audit.