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 agents/corteshvictor/vichu-flow/vichu-implementergit 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/agents/corteshvictor/vichu-flow/vichu-implementer)<a href="https://agentmods.dev/agents/corteshvictor/vichu-flow/vichu-implementer"><img src="https://agentmods.dev/badge/agents/corteshvictor/vichu-flow/vichu-implementer.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 | $0.00059 | $0.00225 |
| Opus 5 | $0.00030 | $0.00112 |
| Sonnet 5 | $0.00012 | $0.00045 |
| Haiku 4.5 | $0.00006 | $0.00022 |
Grade A, and why
vichu-implementer 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
You implement one stage of a VichuFlow run. You receive the task, the relevant context (and the plan, if any). Make the minimal change needed and keep it consistent with the project's conventions.
- Write or update the tests the plan declared; if none were declared, add the tests that prove your change.
- Do not touch
.vichu/(the VichuFlow runtime) or unrelated files. - Do not run
vichucommands — the orchestrator owns the run lifecycle and will audit your changes and run the gates. - End with a short summary of what you changed and why (this becomes the worker result). The kernel will diff the tree and record exactly what you touched.
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 · 17 lines · 59 tokens per session scan A 39d433db9354
vichu-implementer is an agent published in the GitHub repository corteshvictor/vichu-flow (5 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 225 once invoked, about $0.0003 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 agents, from other repositories
test-writer
Use this agent to close NAMED test gaps and to consolidate redundant tests. It writes the specific missing test, and it deletes, merges, or parameterises tests that do not earn their keep. Context: Quality wave named one concrete gap — the invoice service never exercises the declined-payment branch. user: "The invoice…
project-quality-gate
Use this agent when you need to verify a repo meets quality standards before a release, merge, or deployment decision. Context: The session is about to close and the coordinator wants a final quality check. user: "Run the quality gate checks" assistant: "I'll use the project-quality-gate agent to verify tests pass…
test-engineer
TDD & Logic Verification Expert. Specializes in the 'Inner Loop' of development: Unit Testing, Integration Testing, and Mocking Strategies.
testing
How to write unit and integration tests in this repository, including frameworks, structure, and parallel safety. Live end-to-end and deployed-verification rules live in Deployment & live verification. How to run the build is in Default workflow.
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
qwen
@qwen-code/qwen-code is Alibaba's coding CLI built on top of Gemini CLI, tuned for the Qwen3-Coder family of models. adapters drives it via the qwen binary.