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/plan)<a href="https://agentmods.dev/commands/jcarlosrodicio/opencode-agent-orchestration-kit/plan"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/plan/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/plan"><img src="https://agentmods.dev/badge/commands/jcarlosrodicio/opencode-agent-orchestration-kit/plan.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.00000 | $0.00717 |
| Opus 5.5 | $0.00000 | $0.00287 |
| Sonnet 5.5 | $0.00000 | $0.00143 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
plan 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective:
$ARGUMENTS
Run a deterministic plan-only flow.
Contract: lead -> researcher -> specifier -> reviewer.
Init/context policy
Before invoking researcher, record only the minimum context:
cwd: target repository or area.AGENTS.md: applicable local rules when present.git state: clean/dirty state when the plan depends on current changes.validation commands: likely checks the plan should use.repo docs: local docs relevant to research/spec.
Do not implement or do deep discovery in this phase.
Mandatory flow
- Ground the user objective with assumptions, questions, scope, non-scope, and verifiable success criteria.
- Always invoke
researcherfirst; wait for the full result before continuing. - Synthesize research findings: verified facts, inferences, risks, recommended decisions, and open questions.
- Invoke
specifieronly after research has been consolidated. - Ask
specifierfor an implementation-ready plan, acceptance criteria, validation, and ordered tasks. - Invoke
reviewerto review the plan/spec against the objective, research, assumptions, risks, and acceptance criteria. - If
reviewerfinds no significant issues, deliver the final plan. - If
reviewerfinds significant issues, allow exactly 1 correction pass. - After the second review, deliver the plan with explicit risks or declare the state blocked.
Dependency rules
- Do not invoke developer.
- Do not invoke
designer; if the work needs design, mark that dependency in the plan or recommend/designor/feature. - Do not implement code or modify application files.
- Do not invoke
specifierwhileresearcherhas pending work. - Do not invoke
reviewerbefore a reviewable plan/spec exists. - Do not use
evaluator,debugger, orevolver; this command plans, it does not evolve or validate the harness. - Do not parallelize phases; this flow is sequential by design.
- If there is a blocking question, stop the flow and state it instead of inventing a decision.
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 · 75 lines · 0 tokens per session scan A 22d8930e27b6
plan is a command published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (136 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 717 tokens. 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
dispatch-worker
Retired Pattern Z Worker loop; use cli-hierarchy (RFC-0051) instead. See docs/operations/cli-hierarchy.md. AISDLC-763.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
patterns
Report observed outcomes, missing data, and possible drift without causal promotion.
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
validate-idea
Test a Shopify app idea using narrow evidence and a small experiment.