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 skills/danielvm-git/bigpowers/scope-worknpx skills add danielvm-git/bigpowers --skill scope-workgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00071 | $0.00936 |
| Opus 5 | $0.00036 | $0.00468 |
| Sonnet 5 | $0.00014 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
scope-work 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e03s01
story: e24s02
Scope Work
Spine position: Step 1 — scope-work → slice-tasks → plan-work.
Turn the current conversation into a bounded PRD at specs/product/SCOPE_LATEST.yaml. Without a scope boundary, implementation drifts — stories expand, estimates blow up, and "done" becomes undefined.
Pre-flight
- Do you have a clear user need or problem statement? If not, run
elaborate-specfirst. - Does
specs/product/VISION_LATEST.yamlexist? If yes, read it for north-star alignment. - Is there an existing
SCOPE_LATEST.yaml? If yes, you're refining, not creating from scratch.
Process
-
Read planning-context.yaml — If
specs/planning-context.yamlexists, read it before doing anything else:test -f specs/planning-context.yaml && echo "Context found" || echo "No context — starting fresh"Pre-populate
feature_name,constraints, andout_of_scopefrom the file. Skip re-asking questions already answered by elaborate-spec. If the file is absent, proceed normally. -
Gather context — Read existing
specs/artifacts (release-plan.yaml,plans/TECH_STACK_LATEST.md,requirements/VISION_LATEST.yamlif any). Understand what the project is building and why. -
Interview (if needed) — Clarify: What is the goal? Who are the users? What is definitely in scope? What is explicitly out of scope? What constraints exist (time, budget, tech)? How will success be measured?
-
Write
specs/product/SCOPE_LATEST.yamlwith these fields:core_value— one-sentence value propositionsummary— 2-3 paragraph scope overviewin_scope[]— list of what this initiative covers (each maps to an epic/story)out_of_scope[]— explicit exclusions (prevents scope creep)constraints— tech, time, resource boundariessuccess_criteria— observable outcomes that prove the scope is deliveredreferences— links to related specs, ADRs, or documents
-
Lightweight trade-off analysis — For each
out_of_scopeitem, note why it's excluded (deferred, not valuable, too risky, depends on external factor). This protects against "what about X?" questions later.
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 · 64 lines · 71 tokens per session scan A 43f439353b98
scope-work is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 71 tokens to every session and 936 once invoked, about $0.0004 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 skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".