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/jcarlosrodicio/opencode-agent-orchestration-kitWrote 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/jcarlosrodicio/opencode-agent-orchestration-kit/test)<a href="https://agentmods.dev/commands/jcarlosrodicio/opencode-agent-orchestration-kit/test"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/test/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/jcarlosrodicio/opencode-agent-orchestration-kit/test"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/test.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.00269 |
| Opus 5.5 | $0.00006 | $0.00108 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (136 stars, last pushed 20d ago), licensed Apache-2.0. It adds 15 tokens to every session and 269 once invoked, about $0.0001 per session on Opus 5.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
p5-impl-red
Writes unit tests for a feature BEFORE production code exists. Tests must fail.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
p5-impl-green
Writes the minimal production code that makes the existing tests green. No over-engineering.
tdd
Test-driven development with TodoWrite planning and comprehensive testing.
rust-test
Rust TDD workflow with unit and property tests.