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.
npx skills add gtapps/hermitd --skill deep-divegit 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/skills/gtapps/hermitd/deep-dive)<a href="https://agentmods.dev/skills/gtapps/hermitd/deep-dive"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/deep-dive/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/skills/gtapps/hermitd/deep-dive"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/deep-dive.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.00080 | $0.00904 |
| Opus 5.5 | $0.00032 | $0.00362 |
| Sonnet 5.5 | $0.00016 | $0.00181 |
| Haiku 4.5 | $0.00008 | $0.00090 |
Grade A, and why
deep-dive 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deep-dive — 91% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Dive
Deliver a focused follow-up analysis for a topic slug referenced in a recent brief.
Input
The argument is the slug from the brief CTA (e.g., local-first-sync, apex-one-zero-day).
Steps
-
Resolve the item. Glob
.hermit/briefs/for files from the last 14 days (sort by date, newest first). Scan each for the slug (case-insensitive substring match against the brief body). Extract the surrounding paragraph — the item's headline, description, any URL, and its category/tags. -
Web research. Using the URL and headline from the brief (if found), run 1–2 targeted WebFetch calls to reach the primary source. If no URL is available, use the slug as a search hint. Collect what the analysis template needs: what happened, key facts/dates, current status, and (for security items) CVE/CVSS, affected versions, exploitation status, patch status.
-
Write the analysis. ≤10–15 lines. Pick the template by the briefed item's nature:
Default (general follow-up) — for any non-security item:
**Deep dive: <slug>** **What happened:** One–two sentences on the development and its context. **Why it matters:** Concrete stakes — who's affected, what decision it informs. **Trajectory:** Where this is heading; what to watch next. **Sources:** Primary link(s) and any useful discussion.Security variant — use ONLY when the briefed item is security-tagged (its category/tags in the brief indicate security, or it's a vulnerability/exploit/breach item):
**Deep dive: <slug>** **What it is:** One sentence — vulnerability type, product, CVE if applicable. **Severity:** CVSS score (if known) + exploitation status. **Who's affected:** Systems/versions/configs at risk. **What attackers can do:** Concrete impact (RCE, cred theft, privilege escalation, etc.). **Exploitation status:** PoC public / in-the-wild / CISA KEV / theoretical. **Patch/mitigation:** Version to upgrade to, workaround if patch unavailable. **Timeline:** Disclosed → PoC → exploitation → patch (key dates only). **Bottom line:** One sentence — patch now / monitor / low priority.
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.
- 11d ago First seen · 75 lines · 80 tokens per session scan A 36aabe2b6114
deep-dive is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 904 once invoked, about $0.0003 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 skills, from other repositories
vigil-instrument
Instrument a service with OpenTelemetry — RED metrics, structured logs, distributed tracing, and health checks. Outputs actual code and config, not a plan. Use when asked to "add monitoring", "instrument this", "add logging", "set up tracing", or "observability".
pave-env
Set up local development environments — devcontainers, Docker Compose, one-command setup, dev/prod parity. Use when asked to "set up dev environment", "devcontainer", "docker compose for dev", "local development setup", or "one command to run".
design-system-reference
Style guides and implementation rules for frontend design. Works with design-discovery agent which handles context gathering and VS-based style recommendations. Contains detailed style guides, anti-patterns, and implementation checklists.
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
magic-compact
Compact this Claude Code session.