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/gtapps/hermitdWrote 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/gtapps/hermitd/hermitd-dev)<a href="https://agentmods.dev/plugins/gtapps/hermitd/hermitd-dev"><img src="https://agentmods.dev/badge/plugins/gtapps/hermitd/hermitd-dev/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/gtapps/hermitd/hermitd-dev"><img src="https://agentmods.dev/badge/plugins/gtapps/hermitd/hermitd-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hermitd-dev 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 3d 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": "hermitd-dev",
"version": "0.4.21",
"dependencies": [
{
"name": "hermitd",
"version": "^1.4.12"
}
],
"description": "Git safeguards, debugging, and merge-conflict resolution for your Hermit.",
"author": {
"name": "gtapps",
"url": "https://github.com/gtapps"
},
"license": "MIT",
"keywords": [
"development",
"git-safety",
"code-review",
"gtapps"
],
"homepage": "https://github.com/gtapps/hermitd/tree/main/plugins/hermitd-dev",
"repository": "https://github.com/gtapps/hermitd"
}
What it installs
The manifest is a name and a version. 4 skills, 1 hook travel with it, and installing the plugin installs all of them — 158 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.
- 3d ago Changed dc9b8ad5c489
- 6d ago Changed d7e5de39ff11
- 11d ago First seen · 25 lines scan A cc0bda94d453
hermitd-dev is a plugin published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), 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-10-02.
Other plugins, from other repositories
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
sre-bot
SRE triage assistant for plain-English production health and Kubernetes questions in Slack. One pinned upstream Kubernetes MCP connector exposes the core toolset: reads execute immediately, six mutations require a fresh human approval, and unmatched tools fail closed. Kubernetes RBAC limits writes to disposable…
dark-factory
Curie's default dark factory agent: one labelled GitHub issue in, one reviewed pull request or one stated reason out. One agent reads the issue through the platform's getissue tool, pins acceptance criteria, plans, gets the plan reviewed by an Opus plan-reviewer subagent, writes a failing test where feasible, implemen.
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
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.