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.
git 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/commands/sairam0424/mindforge/build-vs-buy)<a href="https://agentmods.dev/commands/sairam0424/mindforge/build-vs-buy"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/build-vs-buy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sairam0424/mindforge/build-vs-buy"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/build-vs-buy.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.00500 |
| Opus 5 | $0.00019 | $0.00250 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
build-vs-buy 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 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.
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
<execution_context> @.mindforge/skills/build-vs-buy/SKILL.md </execution_context>
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 · 30 lines · 38 tokens per session scan A afd4430444c8
build-vs-buy is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 500 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-09-03.
Other commands, from other repositories
p3-cost
Estimates the ongoing Operating Costs of the chosen architecture for various usage scenarios. The goal is realistic cost planning that feeds back into the financial plan – no surprises after launch.
p1-financial-plan
Creates a first financial plan with Cost Structure, Revenue Forecast, and break-even analysis. The goal is not exact bookkeeping but a plausible set of numbers that demonstrates the economic viability of the venture.
p6-audit-config
Checks security headers, CORS, DB access, secrets management, and server configuration.
gate-p6-security
Evaluates all security-relevant points of the Gate-P6 checklist and grants Security approval.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.
sdd
Spec-driven dev loop. Plan once, then dev↔test↔eval loop until PRP spec satisfied. Local only, no PR.