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/gate-tracenpx skills add danielvm-git/bigpowers --skill gate-tracegit 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.00054 | $0.01112 |
| Opus 5 | $0.00027 | $0.00556 |
| Sonnet 5 | $0.00011 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
gate-trace 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate Trace
Deterministic quality gate that combines traceability coverage and blind-spot data into a single PASS/FAIL/CONCERNS/WAIVED decision before release.
Decision Rules
| Rule | Condition | Verdict |
|---|---|---|
| R1 | Any undone story with 0 code tags | FAIL |
| R2 | Any story done but no verify evidence | CONCERNS |
| R3 | P0 story (top WSJF quartile) with 0% coverage | FAIL |
| R4 | Overall coverage < 60% | CONCERNS |
| R6 | P0 story + eNN-TEST_PLAN_LATEST.md exists + zero SC-eNNsYY-P0-* in test files | CONCERNS |
| R5 | Overall ≥ 80% + no critical gaps + all verify → PASS | PASS |
Oracle Confidence Downgrade
TEA-inspired: if trace links rely on heuristics rather than explicit tags, confidence drops.
| Heuristic Ratio | Downgrade |
|---|---|
| > 50% links from heuristics (file-name or task-reference) | One level (PASS→CONCERNS, CONCERNS→FAIL) |
| > 80% links from heuristics | Two levels (PASS→FAIL, CONCERNS→FAIL) |
Process
- Pre-flight: Ensure
scripts/trace-stories.sh --jsonhas been run (producesspecs/traceability-matrix.json). If not present, run it. - Ensure
scripts/check-blind-spots.shhas been run (producesspecs/blind-spots.json). If not present, run it. - Read
specs/traceability-matrix.jsonandspecs/blind-spots.json. - Apply decision rules R1–R5 in order (first match wins).
- Apply oracle confidence downgrade based on the heuristic link ratio from the matrix's
oracle_stats. - Drift check (e39s03): If
specs/drift-report.jsonexists and has suspect links, mark verdict as CONCERNS with note: "Drift detected — some implementing files are newer than their specs. Run scripts/check-spec-drift.sh for details." - Output verdict + rationale to stdout.
- Adversarial refute check (e45s32): Before emitting PASS, attempt to refute the verdict — list at least one concrete traceability gap that would block merge if it were real. If the gap is real, downgrade the verdict. Rubber-stamping is prohibited; every PASS must survive one refutation attempt.
- Completeness critic (e45s05) — Run adversarial gap-finding:
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 · 93 lines · 54 tokens per session scan A bd38b767efca
gate-trace is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 54 tokens to every session and 1,112 once invoked, about $0.0003 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".