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/implementgit 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.00005 | $0.00046 |
| Opus 5 | $0.00003 | $0.00023 |
| Sonnet 5 | $0.00001 | $0.00009 |
| Haiku 4.5 | $0.00001 | $0.00005 |
Grade A, and why
implement 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
Implement this approved task:
$ARGUMENTS
Respect the spec, keep changes small, run validation, and summarize the diff. Use TDD when feasible.
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 · 12 lines · 5 tokens per session scan A 813607f8b0e3
implement 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 5 tokens to every session and 46 once invoked, about $0.0000 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-teammate-role
Prime the Teammate 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.
update
Bring this machine to latest main — sync deps, verify environment, restart services. Runs deterministically via inline bash execution, not model discretion.
psm
/oh-my-claudecode:psm is a compatibility alias for /oh-my-claudecode:project-session-manager.