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/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/cmd-plan)<a href="https://agentmods.dev/rules/nota-america/forgecat-agent-profiles/cmd-plan"><img src="https://agentmods.dev/badge/rules/nota-america/forgecat-agent-profiles/cmd-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/nota-america/forgecat-agent-profiles/cmd-plan"><img src="https://agentmods.dev/badge/rules/nota-america/forgecat-agent-profiles/cmd-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.00139 | $0.00139 |
| Opus 5.5 | $0.00056 | $0.00056 |
| Sonnet 5.5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
cmd-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.
What it actually says
Invoke the agent-skills:planning-and-task-breakdown skill.
Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then:
- Enter plan mode — read only, no code changes
- Identify the dependency graph between components
- Slice work vertically (one complete path per task, not horizontal layers)
- Write tasks with acceptance criteria and verification steps
- Add checkpoints between phases
- Present the plan for human review
Save the plan to tasks/plan.md and task list to tasks/todo.md.
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 · 19 lines · 139 tokens per session scan A fc664e256398
cmd-plan is a cursor rule published in the GitHub repository nota-america/forgecat-agent-profiles (93 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 139 tokens to every session, about $0.0006 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-08-30.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.