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/NikiforovAll/claude-code-rulesWrote 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/nikiforovall/claude-code-rules/handbook-git-worktree)<a href="https://agentmods.dev/plugins/nikiforovall/claude-code-rules/handbook-git-worktree"><img src="https://agentmods.dev/badge/plugins/nikiforovall/claude-code-rules/handbook-git-worktree/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/nikiforovall/claude-code-rules/handbook-git-worktree"><img src="https://agentmods.dev/badge/plugins/nikiforovall/claude-code-rules/handbook-git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
handbook-git-worktree 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 1mo 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": "handbook-git-worktree",
"version": "1.19.5",
"description": "Git worktree management for working on multiple branches simultaneously",
"author": {
"name": "nikiforovall",
"url": "https://github.com/nikiforovall"
},
"homepage": "https://nikiforovall.blog/claude-code-rules/",
"repository": "https://github.com/nikiforovall/claude-code-rules",
"license": "MIT",
"keywords": [
"git",
"worktree",
"branches",
"productivity",
"workflow",
"parallel-development"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 57 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.
- 1mo ago First seen · 21 lines scan A be23b6424860
handbook-git-worktree is a plugin published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 15d ago), licensed Apache-2.0. 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-08-30.
Other plugins, from other repositories
review-pr
Review PRs in a Tour Guide (expository) or Adversarial (audit) posture, with logical file ordering, context, and severity-rated findings. Forge-agnostic (GitHub + Bitbucket).
dev-tools-plugin
General developer tooling — read-only thinking and Q&A, git workflows, code hygiene, dependency management, and project documentation generation. Every skill is user-invoked only: Claude never starts a merge, an upgrade or a docs rewrite on its own.
odin
ODIN - advanced code agent with diagram-first engineering and atomic commit workflows for surgical precision in software development.
issue-to-pr
Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session…
agent-dispatch
Start issue-to-pr runs from GitHub labels on your own machine: a scheduled tick picks the issue you labelled agent, or the one you replied on, and runs it headless under your own Claude Code or Codex login, on Windows, macOS or Linux.
axiom-git
Composes Conventional Commits messages with gitmoji from the staged diff, deciding type, scope, emoji, subject, and body, and gating on protected branches, staged secrets, and pre-commit hooks.