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 skills add sairam0424/MindForge --skill mindforge-reviewgit clone --depth 1 https://github.com/sairam0424/MindForgeWrote 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/sairam0424/mindforge/mindforge-review)<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-review"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-review.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.00018 | $0.00225 |
| Opus 5 | $0.00009 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
mindforge-review 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 4d 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
Flow: Detect CLIs → Build review prompt → Invoke each CLI → Collect responses → Write REVIEWS.md
<execution_context> @.agent/workflows/mindforge-review.md </execution_context>
Flags:
--gemini— Include Gemini CLI review--claude— Include the agent CLI review (uses separate session)--codex— Include Codex CLI review--all— Include all available CLIs
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.
- 4d ago First seen · 32 lines · 18 tokens per session scan A 704eea27c7f9
mindforge-review is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 225 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-09-03.
Other skills, from other repositories
ap-reviewer
L3 independent G2/G5 or roadmap reviewer - checks mission coverage, reality, tests, boundaries, and claim-vs-diff; returns binary SMASH or PASS.
ap-sweeper
L3 executor - SWEEP. Fresh production-readiness sweeper that re-derives mission coverage, inspects the changed neighborhood, checks GATELOG provenance, and returns evidence-backed P0..P3 findings.
Systematic debugging
Use when you hit a bug, test failure, or unexpected behavior — find the root cause before changing code.
Verify before done
Use before claiming work is complete — prove it with commands, do not assume.
pr
A workflow for analyzing branch changes and creating a draft pull request, including a screenshot step when the changes affect the user interface.
ablate
An ablation workflow for testing a harness by removing one element at a time and measuring whether that element changes the result. A harness is the surrounding setup used to run and evaluate a system.