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/audit-plannpx skills add danielvm-git/bigpowers --skill audit-plangit 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.00055 | $0.00876 |
| Opus 5 | $0.00028 | $0.00438 |
| Sonnet 5 | $0.00011 | $0.00175 |
| Haiku 4.5 | $0.00006 | $0.00088 |
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 3d 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 — 90 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.
- 3d ago First seen · 90 lines · 55 tokens per session scan A 49f06a4f4ead
audit-plan is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 26d ago), licensed MIT. It adds 55 tokens to every session and 876 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
pm/competitive-analysis
竞品调研和分析方法，通过系统性分析竞品的功能、体验和策略，发现差异化机会.
macrothink
User-invoked read-only pass for checking whether the current direction is tunnel-visioned: strip the session's bait, fan out 2 to 5 same-model fresh reads, and report divergence first without treating convergence as proof.
nba
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
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-domain-research
Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]".
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.