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/zerocracy/zealotWrote 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/zerocracy/zealot/zealot)<a href="https://agentmods.dev/plugins/zerocracy/zealot/zealot"><img src="https://agentmods.dev/badge/plugins/zerocracy/zealot/zealot/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/zerocracy/zealot/zealot"><img src="https://agentmods.dev/badge/plugins/zerocracy/zealot/zealot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
zealot 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
{
"author": {
"email": "[email protected]",
"name": "Yegor Bugayenko"
},
"description": "Seven skills for disciplined GitHub workflows: filing bugs, triaging issues, writing commit messages, submitting pull requests, reviewing pull requests, responding to inbound comments on issues and pull requests, and orchestrating one daily contribution",
"homepage": "https://github.com/zerocracy/zealot",
"keywords": [
"skills",
"github",
"code-review",
"pull-requests",
"bug-reports",
"commits",
"automation"
],
"license": "MIT",
"name": "zealot",
"repository": "https://github.com/zerocracy/zealot",
"version": "0.1.0"
}
What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 239 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 22 lines scan A 28627703edd8
zealot is a plugin published in the GitHub repository zerocracy/zealot (4 stars, last pushed yesterday), 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-08-31.
Other plugins, from other repositories
pipecat-dev
Development workflow skills for contributing to the Pipecat project.
fix-all
Run bin/claude-review --print and automatically fix all reported issues, committing each fix individually.
han-github
Github specific extensions to the Han plugin for agentic planning and coding. Provides skills to post code reviews as PR comments, update a PR description with a consistent format, etc.
odin-git
ODIN workflows for commits, branches, pull requests, review feedback, and issue tracking.
git
Git workflow tools: commits, PRs, review inbox, checkout, and work triage.
review-toolkit
Comprehensive PR review pipeline: a pre-review readiness gate (stops on merge conflicts or red code-related CI with a fix-it note, no verdict), branch-level analysis with merge-base attribution (the verdict is decided only by defects the diff introduced, worsened, or interacts with — purely pre-existing defects are…