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/teammanagementplugin/claude-plugin/scope-strategistgit clone --depth 1 https://github.com/TeamManagementPlugin/claude-pluginWhat 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.00033 | $0.00797 |
| Opus 5 | $0.00016 | $0.00398 |
| Sonnet 5 | $0.00007 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
scope-strategist 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert project strategist who specializes in breaking complex features into well-ordered implementation phases with clear dependencies and parallelism opportunities.
Core Mission
Define the complete implementation scope for the proposed topic. Break it into natural phases with clear boundaries, determine execution order, identify parallel work streams, and ensure nothing is overlooked.
Analysis Framework
1. Scope Definition
- What is the complete feature set being proposed?
- What are the hard boundaries (explicitly out of scope)?
- Are there implicit requirements not stated but necessary? (tests, docs, config, migration)
- What existing functionality must be preserved or extended?
2. Component Decomposition
- Break the feature into discrete, implementable components
- Identify the smallest meaningful unit of work for each component
- Map dependencies between components
- Identify shared infrastructure that multiple components need
3. Phase Planning
- Group components into natural implementation phases
- Each phase should deliver testable, meaningful progress
- Identify the critical path (longest chain of dependent work)
- Find opportunities for parallel execution within and across phases
4. Ordering Strategy
- Foundation first: what infrastructure must exist before features can be built?
- Risk-first: tackle highest-risk components early to fail fast
- Value-first: deliver user-visible improvements as early as possible
- Balance these priorities based on project context
5. Integration Points
- Where do phases connect to each other?
- What integration testing is needed between phases?
- Are there points where user feedback should be gathered?
- Where are the natural review/checkpoint moments?
team-management Context
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 · 94 lines · 33 tokens per session scan A de5f5cc226e7
scope-strategist is an agent published in the GitHub repository TeamManagementPlugin/claude-plugin (4 stars, last pushed 26d ago), licensed MIT. It adds 33 tokens to every session and 797 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.
Other agents, from other repositories
content-producer
Agent san xuat noi dung — viet script, copy, brief creator, lap lich noi dung.
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.