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 rules/danielvm-git/bigpowers/trace-requirementgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/danielvm-git/bigpowers/trace-requirement)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/trace-requirement"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/trace-requirement.svg" alt="Measured on agentmods" height="20"></a>What 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.00058 | $0.00700 |
| Opus 5 | $0.00029 | $0.00350 |
| Sonnet 5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
trace-requirement 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace Requirement
Build a traceability matrix from specs/release-plan.yaml + epic capsule directories to implementing code and tests. Surfaces gaps in both directions: stories with no code, and code with no story.
Pre-flight
HARD GATE —
specs/release-plan.yaml + epic capsule directoriesmust exist. If it doesn't, runplan-releasefirst.
→ verify: test -f specs/release-plan.yaml && test -d specs/epics
Read specs/release-plan.yaml + epic capsule directories fully before proceeding.
Process
1. Extract story IDs
From release-plan.yaml, collect all story IDs (e.g. 1.1, 1.2, 2.1).
→ verify: grep -rho 'e[0-9]\+s[0-9]\+' specs/release-plan.yaml specs/epics/*/epic.yaml 2>/dev/null | sort -u | head -1 | grep -q .
2. Search for story tags in code
Look for // story: X.Y or # story: X.Y comments in source files and tests:
grep -rn "story: " . --include="*.ts" --include="*.js" --include="*.py" --include="*.sh" | grep -v node_modules
→ verify: [ "$(grep -rl "story: " . --include="*.ts" --include="*.sh" --include="*.py" 2>/dev/null | wc -l | tr -d " ")" -gt 0 ]
3. Build the matrix
For each story ID:
- Implemented: list files that contain
// story: X.Y - Tested: list test files that contain
// story: X.Y - Dark: story has no tag in any file — flag as unimplemented
For each tagged file with no matching story ID in release-plan.yaml:
- Orphan: code exists but story was removed or never planned — flag for cleanup
4. Write specs/TRACEABILITY_LATEST.md
## Story Coverage
| Story | Title | Files | Tests | Status |
|-------|--------------------|-------|-------|-----------|
| 1.1 | [title] | 2 | 1 | Covered |
| 1.2 | [title] | 0 | 0 | Dark |
## Orphan Code (no story tag)
- [file]: contains untagged implementation
## Gaps (dark stories)
- Story 1.2: no implementation found → run plan-work
## Coverage summary
Stories: [X] covered / [Y] dark / [Z] total
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 · 69 lines · 58 tokens per session scan A 672fc0fe5250
trace-requirement is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 3d ago), licensed MIT. It adds 58 tokens to every session and 700 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-09-03.
Other cursor rules, from other repositories
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
ai-dev-os-ticket
Generates a ticket (local file or GitHub Issue) with implementation summary and checklist candidates derived from AI Dev OS guidelines. Used to create structured implementation tasks.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.
project-journal
After significant milestones, offer to append a dated row to PROJECTJOURNAL.md (task, state/debt, next steps).