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.
git 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/audit-plan)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/audit-plan"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/audit-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/audit-plan"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/audit-plan.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00052 | $0.00871 |
| Opus 5.5 | $0.00021 | $0.00348 |
| Sonnet 5.5 | $0.00010 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
audit-plan 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Plan
HARD GATE — Do NOT start build skills (kickoff-branch, develop-tdd) until audit-plan returns a READY verdict. A plan missing test commands, scope boundaries, or success criteria will produce drift and rework downstream.
Assess an incoming project plan for alignment with bigpowers principles, identify what's missing, and produce a structured readiness report before any skill execution begins.
Three lenses
1. Principles alignment
- Are stories vertical slices (not horizontal layers)?
- Is scope bounded — explicit in_scope + out_of_scope?
- Are success criteria defined (how do we know we're done)?
- Are HARD GATE candidates identifiable (critical decision points)?
- Is there a domain language / ubiquitous terminology?
2. Conventions completeness
- Does
CLAUDE.mdorAGENTS.mdexist? - Does
CONVENTIONS.mdexist? - Is the
specs/directory layout in place? - Are commit conventions documented (Conventional Commits)?
- Is the git workflow mode identified (
solo-git|team-pr)?
3. Bigpowers pre-flight (must all be answered before build)
| Question | Why |
|---|---|
| What is the test command? | develop-tdd verify steps require it |
| What is the build command? | verify-work mechanical gate |
| What is the lint command? | audit-code lint gate |
| What is the typecheck command? | verify-work typecheck gate |
| What CI platform is in use? | wire-ci configuration |
| Solo or team? | release-branch integration mode |
| Primary language + framework? | model routing + conventions |
| Greenfield or existing codebase? | determines whether to run seed-conventions or migrate-spec first |
Process
-
Ingest the plan — accept a file path, pasted PRD text, or existing
specs/artifacts. ReadCLAUDE.mdandCONVENTIONS.mdif present. -
Score each lens — for every item above, mark:
- ✅ Present and adequate
- ⚠️ Present but incomplete — note what's missing
- ❌ Absent
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.
- 1mo ago First seen · 89 lines · 52 tokens per session scan A a38c53e987fe
audit-plan is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 52 tokens to every session and 871 once invoked, about $0.0002 per session on Opus 5.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
payload-cms
Payload CMS: collections, fields, hooks, access control, admin UI.
monorepo
Monorepo: workspace references, shared packages, boundaries.
pnpm
PNPM: workspace monorepos, efficient package management.
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.
agent-workflow-orchestration
Mandatory PM-orchestrated subagent workflow — main agent is manager, no separate PM subagent.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.