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/commitnpx skills add savedpixel/ai-agent-rules-generator --skill commitgit 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.00040 | $0.00667 |
| Opus 5 | $0.00020 | $0.00333 |
| Sonnet 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 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.
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.
- yesterday 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 (7 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 667 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…