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/wesammustafa/opencode-primerWrote 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/wesammustafa/opencode-primer/test)<a href="https://agentmods.dev/commands/wesammustafa/opencode-primer/test"><img src="https://agentmods.dev/badge/commands/wesammustafa/opencode-primer/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/wesammustafa/opencode-primer/test"><img src="https://agentmods.dev/badge/commands/wesammustafa/opencode-primer/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.00010 | $0.00307 |
| Opus 5.5 | $0.00004 | $0.00123 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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
Run the project test suite and triage failures.
- Detect the runner from the repo and run it:
!cat package.json 2>/dev/null | grep -E '"test"|"scripts"' | head -5
Pick the right command:
pnpm test,npm test,yarn testfor Nodepytest/python -m pytestfor Pythongo test ./...for Gocargo testfor Rust- Other: read the project's
AGENTS.mdfor the canonical command
-
Run the chosen test command with the bash tool and capture the output. (Shell injections like the one above expand before the model runs, so the command you picked in step 1 has to be run as a normal tool call, not a template.)
-
If everything passes, print a one-line summary and stop.
-
If there are failures:
- Group them by file
- For each failing test, open the relevant source and identify the root cause
- Propose a fix (snippet) but do not edit files yet — wait for user approval
- Distinguish between "test is wrong" and "code is wrong"
-
After the user confirms, apply the fixes and re-run the suite to verify.
Extra arguments (passed to the runner): $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.
- 1mo ago First seen · 33 lines · 10 tokens per session scan A 12d0773893b1
test is a command published in the GitHub repository wesammustafa/opencode-primer (402 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 307 once invoked, about $0.0000 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
feature-implement-execute
Phase 4 of develop: Execute the implementation plan with per-task TDD, quality gates, and completion verification.
modernize-uplift
Same-stack version uplift (e.g. .NET Framework 4.8 → .NET 8) — preserve the code, fix the version deltas, prove equivalence by running one test suite on both runtimes.
audit-mirage-analyze
Phases 2-3 and 7 of auditing-green-mirage: systematic line-by-line audit, the Green Mirage Patterns, named assertion shapes, and the fix-verification Test Adversary prompt.
pr-dance
Loop a PR through CI and bot review until merge-ready. Use when user says '/pr-dance', 'do the PR dance', or finishing-a-development-branch dispatches option 3.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
merge-work-packets
Verify all tracks complete, invoke merging-worktrees, run QA gates, report final integration status.