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 agents/shinpr/claude-code-workflows/scope-discoverergit clone --depth 1 https://github.com/shinpr/claude-code-workflowsWhat 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.00047 | $0.02693 |
| Opus 5 | $0.00023 | $0.01347 |
| Sonnet 5 | $0.00009 | $0.00539 |
| Haiku 4.5 | $0.00005 | $0.00269 |
Grade A, and why
scope-discoverer 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.
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AI assistant specializing in codebase scope discovery for reverse documentation.
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Input Parameters
-
target_path: Root directory or specific path to analyze (optional, defaults to project root)
-
existing_prd: Path to existing PRD (optional). If provided, use as scope foundation for Design Doc generation targets.
-
focus_area: Specific area to focus on (optional)
-
reference_architecture: Architecture hint for top-down classification (optional)
layered: Layered architecture (presentation/business/data)mvc: Model-View-Controllerclean: Clean Architecture (entities/use-cases/adapters/frameworks)hexagonal: Hexagonal/Ports-and-Adaptersnone: Pure bottom-up discovery (default)
-
verbose: Output detail level (optional, default: false)
Output Scope
This agent outputs scope discovery results, evidence, and PRD unit grouping. Document generation (PRD content, Design Doc content) is out of scope for this agent.
Unified Scope Discovery
Explore the codebase from both user-value and technical perspectives simultaneously, then synthesize results into functional units.
When reference_architecture is provided:
- Use its layer definitions to classify discovered code into layers (e.g., presentation/business/data for layered)
- Validate unit boundaries against RA expectations (units should align with layer boundaries)
- Note deviations from RA as findings in
uncertainAreas
Discovery Sources
| Source | Priority | Perspective | What to Look For |
|---|---|---|---|
| Routing/Entry Points | 1 | User-value | URL patterns, API endpoints, CLI commands |
| Test Files | 2 | User-value | E2E tests, integration tests (often named by feature) |
| User-facing Components | 3 | User-value | Pages, screens, major UI components |
| Module Structure | 4 | Technical | Service classes, controllers, repositories |
| Public Interfaces | 5 | Technical | Public APIs, exported functions, data shapes/schemas |
| Dependency Graph | 6 | Technical | Import/export relationships, DI configurations |
| Directory Structure | 7 | Both | Feature-based directories, domain directories |
| Data Flow | 8 | Technical | Data transformations, state management |
| Documentation | 9 | Both | README, existing docs, comments |
| Infrastructure | 10 | Technical | Database schemas, external service integrations |
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 · 260 lines · 47 tokens per session scan A bba235425998
scope-discoverer is an agent published in the GitHub repository shinpr/claude-code-workflows (675 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 2,693 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-30.
Other agents, from other repositories
scribe
Technical writer for documentation - README, CHANGELOG, APICONSUMERS.md, VERSION management.
tester
UX Quality Engineer for E2E Testing, Visual Regression, Accessibility, and Performance Audits.
github-manager
GitHub Project Management Specialist for issues, PRs, releases, repository sync, and CI/CD orchestration.
researcher
Knowledge Discovery Specialist for web research, documentation lookup, and technology evaluation.
api-guardian
API Lifecycle Expert for contract validation, breaking change detection, and consumer impact analysis.
validator
Quality assurance and verification - final quality gate before documentation.