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/jcarlosrodicio/opencode-agent-orchestration-kit/testgit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWhat 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.00015 | $0.00269 |
| Opus 5 | $0.00008 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
test 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 2d 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
Test objective:
$ARGUMENTS
Use the matching local skills:
test-driven-developmentfor behavior changes, bugs, or new tests.debugging-and-error-recoverywhen there is a failure, trace, or unexpected behavior.
Flow:
- Identify expected behavior, scope, and success criteria.
- For bugs, reproduce first with a test or observable evidence.
- Add or adjust the minimum test that proves the behavior.
- Run the narrowest useful validation.
- If implementation is needed to make the test pass and scope is clear, implement the minimum code required.
- Run final reasonable validation and summarize the evidence.
Rules:
- Do not replace
/featurewhen spec, research, or scope decisions are missing. - Do not write tests that only verify fragile internals.
- Do not claim success for a reproducible bug unless you saw the new test fail, unless you explain why that was not viable.
- Do not expand refactors beyond the tested behavior.
Deliver:
- Test or validation added.
- Before/after result when applicable.
- Implementation changes, if any.
- Commands run.
- Risks or pending coverage.
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.
- 2d ago First seen · 41 lines · 15 tokens per session scan A 858925f9c0f3
test is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (105 stars, last pushed 4d ago), licensed Apache-2.0. It adds 15 tokens to every session and 269 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-30.
Other commands, from other repositories
prime-pm-role
Prime the PM (project manager) persona for the headless session runner. Receives the user message as $ARGUMENTS.
_prime-rails
These rails apply to every session-runner session (PM, Dev, and Teammate roles). Each role prime instructs you to read and apply this file before acting.
prime-dev-role
Prime the Dev (developer) persona for the headless session runner. No task is present in $ARGUMENTS — the runner will relay the PM's first instruction separately.
prime-teammate-role
Prime the Teammate persona for the headless session runner. Receives the user message as $ARGUMENTS.
update
Bring this machine to latest main — sync deps, verify environment, restart services. Runs deterministically via inline bash execution, not model discretion.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.