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/savedpixel/ai-agent-rules-generatorWrote 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/savedpixel/ai-agent-rules-generator/commit)<a href="https://agentmods.dev/rules/savedpixel/ai-agent-rules-generator/commit"><img src="https://agentmods.dev/badge/rules/savedpixel/ai-agent-rules-generator/commit/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/savedpixel/ai-agent-rules-generator/commit"><img src="https://agentmods.dev/badge/rules/savedpixel/ai-agent-rules-generator/commit.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.01067 | $0.01067 |
| Opus 5.5 | $0.00427 | $0.00427 |
| Sonnet 5.5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
commit 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Rules
Stage, commit, and push only the files you modified in this chat session to the current working branch. Do not include files changed by other tasks or tools.
Branch Safety (BLOCKING GATE)
- Check the current branch — run
git branch --show-current. - If on
masterormain— STOP immediately. Do not stage, commit, or push. Tell the user and wait. - If on
dev— you may commit, but do NOT push automatically. After committing, ask: "Committed. Ready to push to dev?" Wait for explicit approval. - Stay on the branch you started on. Never switch branches just to commit.
- Never push or commit directly to
masterormainunless explicitly instructed.
Verification Gate (BLOCKING)
Before committing, confirm that ALL required verification steps from the task plan have passed. If any verification is blocked or incomplete, do NOT commit. Report the blocker. See task.mdc → Blocker Protocol.
Steps
-
Check
git status --short— Review all modified and untracked files. Identify which ones you touched. -
Stage only your files — Use
git addwith explicit file paths. Never usegit add -Aorgit add .because they can capture unrelated changes. -
Write a high-quality commit message using multiple
-mflags. Never use one long quoted multi-line string.Commit Subject Rules
<type>(<optional-scope>): <action-oriented summary>Allowed Types:
feat,fix,refactor,docs,style,data,config,chore,mergeCommit Subject Standards
- Keep subjects under ~80 characters.
- Use lowercase for type and scope.
- Start with a clear verb (add, fix, move, remove, migrate, refine, etc.).
- Be specific, not generic.
- For multi-change sessions: summarize themes, put details in body.
Commit Body Rules
Use additional
-mflags for body. Keep to 2–3-mflags total.The body should:
- Summarize key changes in one short paragraph (3–5 sentences max)
- Mention most important modules or areas
- Explain why if not obvious
- Never enumerate every single change
- End with
Files: <key files touched>
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 · 113 lines · 1,067 tokens per session scan A 00892bbe0cc7
commit is a cursor rule published in the GitHub repository savedpixel/ai-agent-rules-generator (8 stars, last pushed 6mo ago), licensed MIT. It adds 1,067 tokens to every session, about $0.0043 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-31.
Other cursor rules, from other repositories
project-rules
Cursor rule "project-rules" from peva3/anchor, covering cursor ai rules, core directives, critical enforcements, pre-commit checklist and required folders.
git-workflow
Cursor rule "git-workflow" from comet-ml/opik, covering git workflow, branch naming, commit format, pr title and pr body.
windsurfrules
Pare wraps CLI tools in MCP servers returning structured JSON. Always prefer Pare MCP tools over raw CLI.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
git-workflow
Git workflow: commits, branches, PRs, history management.