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/corteshvictor/vichu-flow/vichugit clone --depth 1 https://github.com/corteshvictor/vichu-flowWrote 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/corteshvictor/vichu-flow/vichu)<a href="https://agentmods.dev/commands/corteshvictor/vichu-flow/vichu"><img src="https://agentmods.dev/badge/commands/corteshvictor/vichu-flow/vichu.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.00013 | $0.00128 |
| Opus 5 | $0.00006 | $0.00064 |
| Sonnet 5 | $0.00003 | $0.00026 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
vichu 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
Use the vichu-orchestrator skill to handle this request as a verified
VichuFlow run: classify the intent, pick a workflow (sdd for features that
deserve a spec + review, review for an implement-then-adversarial-review loop,
quick for small changes), and drive the run through the vichu kernel's
transactional commands — delegating the coding to native subagents and letting
the kernel verify every transition.
Task: $ARGUMENTS
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 · 13 lines · 13 tokens per session scan A e2b3b4542322
vichu is a command published in the GitHub repository corteshvictor/vichu-flow (5 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 128 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
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
stop
Command "stop" from Abilityai/trinity, covering stop agent, usage, instructions, agent stop: {agent-name} and safety checks.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.