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/seed-conventions)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/seed-conventions"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/seed-conventions/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/seed-conventions"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/seed-conventions.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.00083 | $0.03609 |
| Opus 5.5 | $0.00033 | $0.01444 |
| Sonnet 5.5 | $0.00017 | $0.00722 |
| Haiku 4.5 | $0.00008 | $0.00361 |
Grade A, and why
seed-conventions 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e10s01
story: e47s02
story: e10s02
story: e51s02
story: e45s21
story: e79s03
Seed Conventions
HARD GATE — Before any new code lands, confirm the project conventions are understood. Ask: 'What does a good commit message look like in this project?'
Bootstrap a new project with the AI agent conventions it needs. Run this once at the start of a greenfield project.
What this creates
CLAUDE.md— Claude Code session config (project-specific)CONVENTIONS.md— shared rules for all AI agentsspecs/— the specs directory where all planning output will liveAGENTS.md— for OpenCode and other agents (optional)GEMINI.md— for Gemini CLI (optional)
Interview
Ask the user these questions (one at a time, wait for each answer):
- Project name and one-sentence description — "What is this project? One sentence."
- Stack — "What language, framework, and runtime? (e.g. TypeScript / Next.js / Node 22)"
2b. Stack profile (optional) — Offer:
swift,typescript-vue,node-service, or none. If chosen, merge the matching fragment fromprofiles/<name>.mdinto generatedCONVENTIONS.md. - Commands — "What commands do you use for: run, test, build, lint?" 3b. Preflight (optional) — "What command runs test, lint, and build together? If none, chain Test + Lint + Build into one Preflight row."
- Architecture — "Key modules and relationships in 1–2 sentences."
- Conventions — "Any naming, file organization, or patterns all agents must follow?"
- Never-do list — "What are the hard stops? Things an agent must never touch?"
- Defensive code categories — "Which apply? (Rate limit / Retry / Circuit breaker / Timeout / Graceful degradation)"
- Local tool wiring (optional) — "Wire bigpowers for project-local tools? (Cursor, OpenCode, Cline, Aider, Codex CLI)" If yes, generate AGENTS.md spine artifacts per REFERENCE.md §Local tool wiring and §AGENTS.md spine. If no, skip — standard seed output unchanged (no AGENTS.md spine unless opted in).
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 · 312 lines · 83 tokens per session scan A cfa36136c755
seed-conventions is a cursor rule published in the GitHub repository danielvm-git/bigpowers (267 stars, last pushed 27d ago), licensed MIT. It adds 83 tokens to every session and 3,609 once invoked, about $0.0003 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.