A project-scoping command that refines one living note in a vault, a collection of stored project information. It keeps a required list of unknowns and open questions as the project becomes clearer.

Use it to investigate and shape a project, revisit an existing scope note, record findings, and track questions that still need answers. It can use repository context when run inside a Git project.

It gives discovery work a durable place to live across sessions instead of scattering decisions across separate notes. It also makes unresolved questions explicit before the project is broken into tasks.

scope — Command for Claude Code by ethanaubuchon

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.

Clone the repo

git clone --depth 1 https://github.com/ethanaubuchon/dossier-tradecraft

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/scope/github.svg)](https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/scope)

Your own site

<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/scope"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/scope/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ethanaubuchon/dossier-tradecraft/scope"><img src="https://agentmods.dev/badge/commands/ethanaubuchon/dossier-tradecraft/scope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,709 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00030	$0.01709
Opus 5	$0.00015	$0.00855
Sonnet 5	$0.00006	$0.00342
Haiku 4.5	$0.00003	$0.00171

Measured 9d ago against content hash e4afdbe7f158, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 9d 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.

commands/scope.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are starting a /scope session. The topic (if provided): $ARGUMENTS

This is the /scope recipe of the dossier-tradecraft framework — project-level scoping/discovery for shaping a project before decomposition.

Principles

Vault is the home. The scope doc lives in the vault as the durable artifact across many sessions. If we're in a repo, that's additive context — not a different destination.
Re-entry is typical. Most invocations refine an existing scope doc rather than creating a new one. Search by tag (scope) + topic, not by path.
Required structural element: an Unknowns/open-questions list. Other sections are agent-driven per project.
Agent-judged writes. Decide slug, structure, and edits directly; surface what was done so the user can redirect post-hoc. No propose-then-approve gates.
Inline integration. Findings during the session land in the scope doc itself, not as separate vault notes.
Loop exits on natural signal. No 3-option decision matrix at every cycle.

Workflow

Load context. Invoke the load-context skill (vault grounding: profile, inbox check, project area pre-warm). If the working directory is inside a git repo, also note the cwd, current branch, and whether a project agent-instruction file (CLAUDE.md, AGENTS.md, etc.) is present, as additional context for the session — no separate primitive needed. Also search for an upstream design doc (tag:design + topic) using mcp__dossier-mcp__search_notes. If one exists, load it and note its status; if status is not ready-for-scope, surface a warning before proceeding — the user may want to revise the design first.
Resolve scope doc. Search the vault for an existing scope doc on this topic.
- Use mcp__dossier-mcp__search_notes with the topic terms; filter for tag:scope if the search supports it, otherwise check the tags field on each candidate.
- 1 match → call mcp__dossier-mcp__get_note to load it, enter EXISTING-DOC MODE.
- >1 match → list candidates briefly (slug + title) and ask the user which to continue with.
- 0 matches → before writing, surface "no existing scope doc found for this topic, creating a new one" so the user can redirect if they expected a match. Then enter NEW-DOC MODE.

Read the full file on GitHub · 90 lines

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.

9d ago First seen · 90 lines · 30 tokens per session scan A e4afdbe7f158

Subscribe to this mod's changes

scope is a command published in the GitHub repository ethanaubuchon/dossier-tradecraft (3 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,709 once invoked, about $0.0002 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-31.

Claude Code Planning agentic-workflows claude claude-skills developer-tools knowledge-management

reflect

Reflect on recent work — log lessons to the journal and propose distilled rule updates for review.

Michael-OvO/obsidian-knowledge-agent · 17 tokens

doctor

Check vault health — broken links, orphans, missing frontmatter, MISSING placeholders — and propose fixes.

Michael-OvO/obsidian-knowledge-agent · 21 tokens

session-start

Thin wrapper (GETSITREP-10) — orientation logic (reading MANIFEST.md/STATUSREPORT.md/PROJECTPLAN.md/.sitrep-data.json, building the summary) lives entirely in getsitrep session-start. This file's only job is to invoke it and show the result — it does not re-read those files or re-derive the summary itself.

viitorohit/sitrep · 0 tokens

scope