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/shalintripathi/organic-osWrote 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/shalintripathi/organic-os/verify-outcome)<a href="https://agentmods.dev/commands/shalintripathi/organic-os/verify-outcome"><img src="https://agentmods.dev/badge/commands/shalintripathi/organic-os/verify-outcome/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/shalintripathi/organic-os/verify-outcome"><img src="https://agentmods.dev/badge/commands/shalintripathi/organic-os/verify-outcome.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.00015 | $0.00038 |
| Opus 5 | $0.00008 | $0.00019 |
| Sonnet 5 | $0.00003 | $0.00008 |
| Haiku 4.5 | $0.00002 | $0.00004 |
Grade A, and why
verify-outcome 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 9d 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 organic-os:hoo-verify-outcome skill and follow it end to end.
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.
- 9d ago First seen · 5 lines · 15 tokens per session scan A 21a20ce46efc
verify-outcome is a command published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 38 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
create-content
Generate SEO + AEO + GEO-optimized content for a topic or keyword.
check-file
Quick SEO + AEO check on the current file or a specified page.
create-topic
Research and generate a complete topic plan with keyword mapping, audience, angle, and competitive positioning.
backlink-gap
Find domains linking to your competitors but not to you, ranked by priority score (DR + link-overlap + traffic + topical relevance) with a four-gate quality scorecard.
rank-aeo
Answer engine optimization. Featured snippets, voice search, People Also Ask.
create-content
Run the full 10-phase content production pipeline — research, draft, fact-check, humanize, and publish.