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/assess-impactgit 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/assess-impact)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/assess-impact"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/assess-impact.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.00063 | $0.00792 |
| Opus 5 | $0.00032 | $0.00396 |
| Sonnet 5 | $0.00013 | $0.00158 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
assess-impact 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 today.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assess Impact
HARD GATE — Run this skill before
plan-workwhenever a change touches an existing module, symbol, or file used by more than one caller. Skip only for net-new code with no existing dependents.
Find the blast radius of the proposed change before a single line is written.
Modes
- Default: full impact analysis (dependents + affected stories + test coverage mapping)
- --lightweight: Fast fan-in/fan-out only (<10s). Maps callers and imports without test coverage mapping. Used by build-epic step 2 as a pre-plan gate. Risk score > 7 triggers a mandatory grill-me session before proceeding.
Process
1. Identify the target
Name the symbol, module, or file being changed. If the user hasn't specified, ask one question: "What exactly are you changing?"
2. Find dependents
grep -rn "[symbol-name]" . --include="*.ts" | grep -v node_modules
git log --oneline -10 -- [file-path]
→ verify: test -f specs/IMPACT_LATEST.md || test -d specs/bugs
3. Map to release plan stories
Read specs/release-plan.yaml + epic capsule directories (if it exists). For each dependent found in Step 2, identify which story owns that module. List stories that will be affected by the change.
→ verify: test -f specs/release-plan.yaml && grep -ci "stor" specs/release-plan.yaml
4. List test coverage
Find tests that exercise the target:
grep -rn "[symbol-name]" . --include="*.test.*" --include="*.spec.*"
→ verify: test -d specs/epics || test -d skills
5. Classify risk
| Level | Condition |
|---|---|
| Low | ≤ 2 callers, all covered by tests |
| Medium | 3–10 callers, partial test coverage |
| High | > 10 callers, or shared API/interface, or no tests |
6. Write specs/IMPACT_LATEST.md
## Target
[symbol or file being changed]
## Dependents ([count])
- [file]: [caller or usage]
## Affected Stories
- Story [X.Y]: [title]
## Test Coverage
- [test file]: covers [scenario]
- Gap: [untested behavior]
## Risk: Low / Medium / High
[One-sentence rationale]
## Recommended action
[Proceed / Add tests first / Discuss design]
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.
- today First seen · 91 lines · 63 tokens per session scan A 9f4e9e51dab7
assess-impact is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 792 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
00-project-rules
ContextOS core project rules and role orchestration.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.