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/change-requestnpx skills add danielvm-git/bigpowers --skill change-requestgit 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.00046 | $0.01193 |
| Opus 5 | $0.00023 | $0.00596 |
| Sonnet 5 | $0.00009 | $0.00239 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
change-request 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 yesterday.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e45s29
story: e20s01
Change Request
HARD GATE —
specs/release-plan.yamlmust exist before running either mode. If it doesn't, runplan-releasefirst.→ verify:
test -f specs/release-plan.yaml
Two modes. State which one you want or the skill will ask.
Mode A — Add
Intake a new requirement mid-flight without disrupting work in progress.
- Capture: What is the change? What problem does it solve?
- Locate: Which existing stories in
specs/epics/does it affect or replace? - Draft: Add story +
tasks[]with Gherkin-style AC in epic YAML (each task hasverify). Tag requirement deltas:ADDED/MODIFIED/REMOVED/RENAMEDwith before/after for non-ADDEDchanges (e45s29). - Place: Append story under existing epic capsule, or create
specs/epics/eNN-slug.yamland register inrelease-plan.yamlepics[]. - Score: Compute WSJF; note if it outranks in-progress work.
→ verify: grep -c 'stories:' specs/epics/*/epic.yaml
Mode B — Reorder
Value-engineering pass over the full release using WSJF.
See REFERENCE.md for the full WSJF scoring rubric.
- Score each epic/story: BV + TC + RR / Job Size.
- Re-sort
release-plan.yamlepics[]and per-epicwsjffields. - Flag cut candidates: WSJF < 1.5.
- Update
specs/release-plan.yamland epicwsjfkeys with rationale. - Report the delta.
→ verify: grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml
Conversational Mode
If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
5-Step Flow
- Capture: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
- Locate: Identify which epic or capability in
specs/epics/the request affects or replaces. - Draft: Present a structured draft of the proposed story and tasks for user confirmation.
- Score: Estimate the WSJF score and explain the calculation so the user understands the priority.
- Place: Confirm the final epic placement with the user before writing files.
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.
- yesterday First seen · 122 lines · 46 tokens per session scan A 53d41a7a79ef
change-request is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 1,193 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 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".