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/rebase)<a href="https://agentmods.dev/plugins/tony/skills/rebase"><img src="https://agentmods.dev/badge/plugins/tony/skills/rebase/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/rebase"><img src="https://agentmods.dev/badge/plugins/tony/skills/rebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
rebase 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 8d 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": "rebase",
"description": "Rebase onto remote trunk with a file-overlap reading before the replay, conflict resolution, and quality gate verification.",
"version": "0.1.0",
"author": {
"name": "Tony Narlock",
"email": "[email protected]"
},
"repository": "https://github.com/tony/skills",
"keywords": [
"git",
"rebase",
"conflicts",
"trunk"
]
}
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.
- 8d ago Changed · +7 lines 8f51ae1a1f97
- 1mo ago First seen · 10 lines scan A 04c103088dbf
rebase 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
git-workflow
Atomic-commit Git workflow skills: folding changes into the right commit (amend/edit/fixup), conflict resolution, reflog-based undo, and bisect debugging, plus shared conventions (rebase-over-merge, stashing, commit-message style).
odh-git
Git utilities, GitHub/GitLab workflow automation, and CI debugging.
ai-modernize
Finds technical debt and anti-patterns in code written with older AI models or vibe coding, and saves a scored report with a prioritized roadmap. Includes a full audit, a quick scan and an agent for unattended runs.
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
git-tools
Git utilities and debugging workflows.
fix-github-issue
Analyzes and fixes GitHub issues using a structured approach with GitHub CLI for issue details, implementing necessary code changes, running tests, and creating proper commit messages.