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.
npx skills add savedpixel/ai-agent-rules-generator --skill commitgit 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/skills/savedpixel/ai-agent-rules-generator/commit)<a href="https://agentmods.dev/skills/savedpixel/ai-agent-rules-generator/commit"><img src="https://agentmods.dev/badge/skills/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/skills/savedpixel/ai-agent-rules-generator/commit"><img src="https://agentmods.dev/badge/skills/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.00040 | $0.00667 |
| Opus 5.5 | $0.00016 | $0.00267 |
| Sonnet 5.5 | $0.00008 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Your Changes
Stage, commit, and push only the files you modified in this session to the current working branch.
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 AGENTS.md → Blocker Protocol.
Steps
-
Check
git status --short— Review all modified/untracked files. Identify which ones you touched. -
Stage only your files — Use
git addwith explicit file paths. Never usegit add -Aorgit add .. -
Write a high-quality commit message using multiple
-mflags.Subject Format
<type>(<optional-scope>): <action-oriented summary>Allowed Types:
feat,fix,refactor,docs,style,data,config,chore,mergeRules:
- Keep subjects under ~80 characters
- Use lowercase for type and scope
- Start with a clear verb
- Be specific, not generic
Body
- 2–3
-mflags max - Summarize key changes in 3–5 sentences
- End with
Files: <key files>
Quick Rewrite Guide
Updated gateway→feat(gateway): add support for digital wallet paymentsfix stuff→fix(checkout): correct redirect URL for cancelled payments
-
Push to the current working branch — If on
dev, ask before pushing.
Rules
- Never stage files you did not change.
- Never use
git add .orgit add -A. - Never use a vague commit subject.
- Do not include Copilot co-author trailers unless explicitly requested.
- Never force push.
- One commit per session batch.
- ALWAYS present 3 commit message options (numbered 1–3, concise → descriptive). Wait for user to pick.
- ALWAYS ask before pushing.
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 · 72 lines · 40 tokens per session scan A b14c246572bf
commit is a skill published in the GitHub repository savedpixel/ai-agent-rules-generator (8 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 667 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-08-31.
Other skills, from other repositories
git-github-flow
Use for branch prep, clean commits, PR descriptions, GitHub issue triage, changelogs, release notes, review response, merge readiness, or publishing a branch safely.
commit
Create a git commit with clear, conventional commit messages. You MUST read this when the user wants to commit staged changes, write a commit message, or finalize code changes with proper conventional commit format since it describes how to follow the user's specific requirements.
atomic-commit
Create honest atomic Git commits by choosing one coherent work batch before editing, keeping the whole repository green, resolving every untracked file, staging the entire root with git add ., and pausing for human review before committing. Use when starting commit-sized work, completing a demonstrable implementation…
git-workflow
Use this skill for anything related to Git and version control workflows. Trigger when the developer asks for help with commit messages, PR descriptions, pull request reviews, branching strategies, changelog generation, release notes, code review etiquette, or Git conventions. Keywords: commit, PR, pull request…
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.