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/mckaywrigley/o1-pro-template-systemWrote 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/mckaywrigley/o1-pro-template-system/general)<a href="https://agentmods.dev/rules/mckaywrigley/o1-pro-template-system/general"><img src="https://agentmods.dev/badge/rules/mckaywrigley/o1-pro-template-system/general/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/mckaywrigley/o1-pro-template-system/general"><img src="https://agentmods.dev/badge/rules/mckaywrigley/o1-pro-template-system/general.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.00007 | $0.00400 |
| Opus 5.5 | $0.00003 | $0.00160 |
| Sonnet 5.5 | $0.00001 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
general 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 yesterday.
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.
What it actually says
Project Instructions
Use specification and guidelines as you build the app.
Write the complete code for every step. Do not get lazy.
Your goal is to completely finish whatever I ask for.
You will see tags in the code. These are context tags that you should use to help you understand the codebase.
Overview
This is a web app template.
Tech Stack
- Frontend: Next.js, Tailwind, Shadcn, Framer Motion
- Backend: Postgres, Supabase, Drizzle ORM, Server Actions
- Auth: Clerk
- Payments: Stripe
- Deployment: Vercel
Project Structure
actions- Server actionsdb- Database related actions- Other actions
app- Next.js app routerapi- API routesroute- An example route_components- One-off components for the routelayout.tsx- Layout for the routepage.tsx- Page for the route
components- Shared componentsui- UI componentsutilities- Utility components
db- Databaseschema- Database schemas
lib- Library codehooks- Custom hooks
prompts- Prompt filespublic- Static assetstypes- Type definitions
Rules
Follow these rules when building the app.
General Rules
- All files should have a comment at the very top of the file that consisely explain what it does
- Use
@to import anything from the app unless otherwise specified - Use kebab case for all files and folders unless otherwise specified
- Don't update shadcn components unless otherwise specified
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.
- yesterday First seen · 59 lines · 7 tokens per session scan A 29c4e086fa4e
general is a cursor rule published in the GitHub repository mckaywrigley/o1-pro-template-system (142 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 400 once invoked, about $0.0000 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-10-14.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.