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/using-bigpowers)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/using-bigpowers"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/using-bigpowers/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/using-bigpowers"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/using-bigpowers.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.00060 | $0.01250 |
| Opus 5.5 | $0.00024 | $0.00500 |
| Sonnet 5.5 | $0.00012 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
using-bigpowers 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using bigpowers
HARD GATE — HARD GATE — This skill is the entry point. Do NOT skip it when onboarding new users or starting a new session. It establishes the bigpowers methodology, lifecycle phases, and conventions.
Welcome to bigpowers — a lifecycle of agent skills for production-ready, TDD-driven software by solo developers. The live catalog and its count are generated in SKILL-INDEX.md; never hardcode the number here.
Install
npx bigpowers setup # one-shot setup
npm install -g bigpowers # global install
bigpowers setup # sync skills + link to your tools
From source: git clone → bash scripts/install.sh. Package: bigpowers on npm.
Reach tools: Cline — native AGENTS.md reader (no extension). Aider — opt-in .aider.conf.yml with read: AGENTS.md (Aider-AI/aider). Codex CLI — optional .codex/config.toml via seed-conventions; global ~/.codex/AGENTS.md from install.sh.
What bigpowers is
A curated set of skills organized around the PMBOK developer lifecycle. Each skill does one thing. Skills reference each other by name only — low coupling, high cohesion. All written output goes to specs/ at your project root.
The lifecycle at a glance
See orchestrate-project for the canonical 6-phase lifecycle.
BOOTSTRAP using-bigpowers (this skill, first time only)
↓
DISCOVER survey-context → research-first → elaborate-spec
↓
DESIGN model-domain / define-language / grill-me / deepen-architecture / design-interface
↓
PLAN scope-work → slice-tasks → plan-work / plan-refactor
↓
INITIATE kickoff-branch → guard-git / hook-commits / seed-conventions
↓
SPIKE? spike-prototype → (feeds back to plan-work)
↓
EXECUTE develop-tdd + enforce-first ←→ delegate-task / dispatch-agents / execute-plan
↓
VERIFY run-evals → verify-work
↓
HARDEN wire-observability (any phase)
↓
BUG? investigate-bug → diagnose-root → validate-fix
↓
REVIEW audit-code → request-review → respond-review
↓
INTEGRATE commit-message → release-branch
↓
SUSTAIN inspect-quality / organize-workspace (ongoing)
UTILITY terse-mode / craft-skill / edit-document (any phase)
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 · 111 lines · 60 tokens per session scan A 9e2ec80da903
using-bigpowers is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 1,250 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
tju-thesis-review-core
A review checklist for final Tianjin University undergraduate theses. It covers submission-critical formatting, page structure, figures, tables, formulas, abstracts, keywords, and references.
tdd
Test-driven development — red-green-refactor cycle.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.