scope

A research-and-specification workflow that turns a task into a small, ordered implementation plan.

In plain words
What is it for?
Inspecting project rules, Git state, documentation, and validation commands, then producing a scoped specification with tasks, acceptance criteria, and a handoff packet.
Why use it?
It gathers the repository context and evidence first, reducing the risk of building the wrong thing or leaving future developers without clear acceptance checks.

Command

Install

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.

agentmods
npx agentmods add commands/jcarlosrodicio/opencode-agent-orchestration-kit/scope
Clone the repo
git clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kit
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 250 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00250
Opus 5 $0.00009 $0.00125
Sonnet 5 $0.00003 $0.00050
Haiku 4.5 $0.00002 $0.00025

Measured 2d ago against content hash dae9bf6aa22c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

scope 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.

opencode/commands/scope.md · 37 lines

What it actually says

I want to research and specify this task:

$ARGUMENTS

Run strictly: researcher -> scoper synthesis -> specifier.

Init/context policy

Before research, fix minimum context:

  • cwd: current repo or target directory.
  • AGENTS.md: applicable local rules when present.
  • git state: clean/dirty state when current changes matter.
  • validation commands: checks that should prove the future spec.
  • repo docs: relevant local documentation.

Rules:

  1. Do not use designer.
  2. Do not use developer.
  3. Do not use reviewer.
  4. Do not implement code.
  5. Invoke researcher first.
  6. Wait for the complete researcher output.
  7. Synthesize findings, risks, decisions, and assumptions.
  8. Invoke specifier only if research is ready for spec.
  9. Ask for scoped specs, not a large macro-spec.
  10. Produce small ordered tasks with acceptance criteria and validation.
  11. Include a Task Contract for future implementation.
  12. Include a handoff_packet when multiple sessions or agents are involved.
Changes

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.

  1. 2d ago First seen · 37 lines · 17 tokens per session scan A dae9bf6aa22c

Subscribe to this mod's changes

scope 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 17 tokens to every session and 250 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.