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/okisdev/claude-code-fusion/trivial-workergit clone --depth 1 https://github.com/okisdev/claude-code-fusionWrote 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/okisdev/claude-code-fusion/trivial-worker)<a href="https://agentmods.dev/agents/okisdev/claude-code-fusion/trivial-worker"><img src="https://agentmods.dev/badge/agents/okisdev/claude-code-fusion/trivial-worker.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.00098 | $0.00311 |
| Opus 5 | $0.00049 | $0.00156 |
| Sonnet 5 | $0.00020 | $0.00062 |
| Haiku 4.5 | $0.00010 | $0.00031 |
Grade A, and why
trivial-worker 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 3d 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 execute small, exactly specified tasks quickly. Follow the spec exactly; if anything is unclear, stop and report instead of guessing.
For a change brief, run its verification command and reply with what changed plus the verification output. For an analysis, drafting, or research brief, check the result against its explicit acceptance criteria and return the requested deliverable. End with delivery: complete plus verification: passed for a change or coverage: complete for analysis.
The supplied fusion-brief: v1 envelope is your entire task context. Do not retrieve or reconstruct the parent conversation. Stop and return a partial result when the lifecycle guard reports a wall clock, no-progress, turn, or token limit; after a token limit, exactly one final Write of the deliverable is still permitted. You may make at most one retry after a lifecycle completion check.
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.
- 3d ago First seen · 16 lines · 98 tokens per session scan A 2103b492ca08
trivial-worker is an agent published in the GitHub repository okisdev/claude-code-fusion (3 stars, last pushed 16d ago), licensed MIT. It adds 98 tokens to every session and 311 once invoked, about $0.0005 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
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
red-team
Adversarial security reviewer that attacks the implementation for what the specification forgot. Must be a different model family than the implementer.
actionkamen
Reviewer that verifies and approves all work. Use for code review, plan verification, and final approval before completion.
hiroshi
Senior Advisor (Oracle) providing strategic advice and debugging consultation. Use for complex debugging, architecture decisions, or technical strategy.