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 agentmods add skills/savedpixel/ai-agent-rules-generator/commit-allnpx skills add savedpixel/ai-agent-rules-generator --skill commit-allgit clone --depth 1 https://github.com/savedpixel/ai-agent-rules-generatorWhat 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 | $0.00036 | $0.00526 |
| Opus 5 | $0.00018 | $0.00263 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
commit-all 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 2d 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
Commit All Uncommitted Changes
Stage, commit, and push all uncommitted changes — grouped by relevance so each commit is cohesive.
Branch Safety (BLOCKING GATE)
- Check the current branch — run
git branch --show-current. - If on
masterormain— STOP immediately. Do not stage, commit, or push. - Stay on the current branch. Never switch branches.
Steps
1. Assess All Changes
git status --short
git diff --stat
2. Group Changes by Relevance
Cluster files into commit batches based on:
- Feature/module area
- Change type (docs, config, source)
- Logical coupling
Target 1–5 batches. If all related, one batch is fine.
3. For Each Batch — Present 3 Commit Message Options
Before committing each batch:
- List the files in the batch
- Present 3 numbered commit message options (concise → descriptive)
- Wait for the user to pick
4. Stage and Commit Each Batch
git add <explicit-file-paths>
git commit -m "<type>(<scope>): <subject>" -m "<body>"
Never use git add . or git add -A. Always explicit paths.
5. Push
After all batches committed:
- Ask: "All batches committed. Ready to push to
<branch>?" - Wait for explicit approval before pushing.
Commit Message Rules
Same rules as the $commit skill:
- Subject:
<type>(<scope>): <summary>— under ~80 chars - Types:
feat,fix,refactor,docs,style,data,config,chore - Body: 2–3
-mflags max, end withFiles:list - 3 options per batch — user picks.
Rules
- Never stage without showing batch contents first.
- Never combine unrelated changes.
- Never skip the 3-option presentation.
- One commit per batch, one push at the end.
- Always ask for explicit user approval.
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.
- 2d ago First seen · 79 lines · 36 tokens per session scan A 62bdefcc65e0
commit-all is a skill published in the GitHub repository savedpixel/ai-agent-rules-generator (7 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 526 once invoked, about $0.0002 per session on Opus 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
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
code-review
Use when user wants code reviewed for correctness, style, bugs, and maintainability. Triggers on: review code, code review, check PR, 審查程式碼, 檢查程式碼. Produces severity-classified findings with a verdict. Do NOT use for security-focused audit (prefer security-audit) or SQL-focused review (prefer sql-review).
plan
Use when user needs a phased implementation plan with requirements, file impact, risks, and alternatives before coding — including clarifying vague or ambiguous requirements first. Triggers on: plan, how should we build, unclear requirements, 規劃, 幫我想方案. Produces a structured plan document. Do NOT use for atomic task…