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 merge-mastergit 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/merge-master)<a href="https://agentmods.dev/skills/savedpixel/ai-agent-rules-generator/merge-master"><img src="https://agentmods.dev/badge/skills/savedpixel/ai-agent-rules-generator/merge-master.svg" alt="Measured on agentmods" 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.00037 | $0.00304 |
| Opus 5 | $0.00018 | $0.00152 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
merge-master 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 7d 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
Merge Dev into Master
Merge the dev branch into master (or main) and push. Includes safety checks.
Steps
-
Ensure all dev changes are pushed — run
git statusandgit log origin/dev..dev. If there are unpushed commits, push them first (with user approval). -
Switch to master/main:
git checkout master # or main git pull origin master -
Merge dev:
git merge dev --no-ff -m "merge(dev→master): <summary>"If there are conflicts, report them and wait for user instructions.
-
Push master:
git push origin master -
Switch back to dev:
git checkout dev
Rules
- Only merge pushed changes. Never merge uncommitted or unpushed work.
- Never force push to master/main.
- If merge conflicts occur, STOP and report. Do not auto-resolve.
- Always push immediately after merging.
- Switch back to dev when done.
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.
- 7d ago First seen · 47 lines · 37 tokens per session scan A 83a3b3c35da5
merge-master is a skill published in the GitHub repository savedpixel/ai-agent-rules-generator (7 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 304 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
worktree-pr
Decide whether a task deserves its own git worktree and, if chosen, run it end to end: branch from the integration branch rather than the current tree, keep the main working copy untouched while the task runs, compare the result against the untouched baseline before declaring it done, and prepare it for a pull request…
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.
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?"…
finishing-a-development-branch
Verifies, summarises, and closes a development branch.
pr-workflow
Prepares branches and PRs for clean, reviewable merges.