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/vidhunnan/agentic-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/vidhunnan/agentic-skills/branch-naming)<a href="https://agentmods.dev/plugins/vidhunnan/agentic-skills/branch-naming"><img src="https://agentmods.dev/badge/plugins/vidhunnan/agentic-skills/branch-naming/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/vidhunnan/agentic-skills/branch-naming"><img src="https://agentmods.dev/badge/plugins/vidhunnan/agentic-skills/branch-naming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
branch-naming 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 4d 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": "branch-naming",
"description": "Suggests and optionally creates a git branch name following the project's convention.",
"version": "0.1.0",
"author": {
"name": "Vidhunnan Murugan"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 88 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.
- 4d ago First seen · 9 lines scan A c76be6505eec
branch-naming is a plugin published in the GitHub repository vidhunnan/agentic-skills (2 stars, last pushed 5d 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-07.
Other plugins, from other repositories
git-pr
Committing, PR creation and review triage, and dependency upgrades.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
lanes-bridges
Bridge Lanes with GitHub and Linear: import issues, batch-spawn a session per ticket, and post results back upstream. Split out of lanes-desktop in 0.7.0.
digest
Summarize AI-generated branches, PRs, and diffs into icon-rich cards, explain code state with git archaeology as self-contained HTML explainers, plus multi-project weekly recall digests.
code-quality
OxLint, Biome, and Prettier configuration, linting skills, and pre-commit hooks for consistent code quality.
peer-review-jj
Unified change review for jj repos — generalist-first with emergent specialists, two-phase pipeline, structured findings.