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/tony/skillsWrote 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/plugins/tony/skills/git-branch)<a href="https://agentmods.dev/plugins/tony/skills/git-branch"><img src="https://agentmods.dev/badge/plugins/tony/skills/git-branch/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/plugins/tony/skills/git-branch"><img src="https://agentmods.dev/badge/plugins/tony/skills/git-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
git-branch 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 5d 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
{
"name": "git-branch",
"description": "Rebuild branch history into atomic commits (byte-identical), or reimplement from scratch using existing tests as the spec. Includes an interactive-rebase toolkit.",
"version": "0.1.1",
"author": {
"name": "Tony Narlock",
"email": "[email protected]"
},
"repository": "https://github.com/tony/skills",
"keywords": [
"git",
"history",
"rebase",
"atomic-commits",
"tdd"
]
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 73 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed f3c8fd6d9df3
- 8d ago Changed · +8 lines 8080ba0fa416
- 1mo ago First seen · 10 lines scan A 9c5701263ca9
git-branch is a plugin published in the GitHub repository tony/skills (0 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
workflow
Developer-workflow commands and skills — sandbox-safe Conventional commits with a commit.sh handoff, immutable code-scanning triage reports with SHA-pinned permalinks, and generation of evolve evaluation suites (triggers + behavioral evals) for agent skills.
es6kr
Reusable AI coding skills: TDD, commit management, dotfile sync, and more.
es6kr
Core fundamental skills: brief, fa, tdd, and web-browser.
engineering-practices
Git commits, conventional releases, refactoring, test-driven development, and engineering ways of working skills.
quatico-skills
Quatico development essentials: commit conventions, PR workflows, TDD, testing, Bitbucket/Jira integration, and team standards.
otter-skills
Portable software-craft skills for thin delivery, TDD, safe change, naming, refactoring, and trustworthy commits.