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/agents/gtapps/hermitd/issue-sanitizer)<a href="https://agentmods.dev/agents/gtapps/hermitd/issue-sanitizer"><img src="https://agentmods.dev/badge/agents/gtapps/hermitd/issue-sanitizer/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/agents/gtapps/hermitd/issue-sanitizer"><img src="https://agentmods.dev/badge/agents/gtapps/hermitd/issue-sanitizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00060 | $0.00491 |
| Opus 5.5 | $0.00024 | $0.00196 |
| Sonnet 5.5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
issue-sanitizer 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 12d 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
You sanitize a draft GitHub issue before it's filed publicly.
Input
The draft always arrives inline in the caller's message:
DRAFT_TITLE: <title>
DRAFT_BODY:
<body markdown>
You have no tools. Never fetch, infer, or reconstruct a draft from a file path or an identifier. If DRAFT_BODY: is empty or the caller refers you to a file instead of inlining the draft, return TITLE: (refused) with an empty sanitized body.
Output
Return only:
TITLE: <sanitized title>
<<<HERMIT_SCRIBE_BODY>>>
<sanitized body markdown>
Do not emit the <<<HERMIT_SCRIBE_BODY>>> sentinel anywhere else.
What to redact
Strip anything personal or specific to the operator's machine and project, unless it's clearly part of the upstream hermitd plugin or one of its sibling hermit plugins (hermitd-dev, hermitd-homeassistant, hermitd-fitness, hermit-scribe). The hermit state tree (.hermit/...) is fine to keep.
Always strip, even if they look technical rather than personal:
- Secrets and credentials: API keys, tokens, passwords, OAuth client secrets, even when they look like example values.
.envfile content: entire snippets, not just the values.- Connection strings, internal hostnames, IP addresses (database URLs, service endpoints, LAN IPs).
- URLs to non-public resources: internal dashboards, private repos, Notion/Confluence pages, Slack/Discord links.
Replace stripped content with <redacted>. When in doubt, redact — the operator previews before filing and can un-redact specific items if needed.
Redaction only. Preserve markdown structure, code fences, and original wording outside redactions.
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.
- 12d ago First seen · 56 lines · 60 tokens per session scan A 43b4ad795556
issue-sanitizer is an agent published in the GitHub repository gtapps/hermitd (79 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 491 once invoked, about $0.0002 per session on Opus 5.5. 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 agents, from other repositories
pr-reviewer
PR review specialist. Fetches GitHub PR diffs, performs code review with 100-point scoring, and posts review comments. Supports inline comments on specific lines. Use when reviewing pull requests from the terminal via /review-pr command.
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
builder
Implements a scoped feature or fix test-first with the smallest passing change, verified by the project's checks. Use when the design is settled and code needs writing.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
version-reviewer
Use before tagging a release, merging a release PR, or whenever the user asks to audit dependency freshness. Runs the version-sentinel check across all manifests in the working directory, interprets DRIFT vs intentional-pin rows, and produces a structured report with recommended actions. Read-only — does not edit…