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/claude-code-hermit --skill source-scoutgit clone --depth 1 https://github.com/gtapps/claude-code-hermitWrote 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/claude-code-hermit/source-scout)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/source-scout"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/source-scout/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/claude-code-hermit/source-scout"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/source-scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.01250 |
| Opus 5.5 | $0.00031 | $0.00500 |
| Sonnet 5.5 | $0.00015 | $0.00250 |
| Haiku 4.5 | $0.00008 | $0.00125 |
Grade A, and why
source-scout 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.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Scout
Proactively discover and add new RSS/web sources to feed-sources.md. Complements source-health
(removal) with discovery (addition). Runs as the source-scout routine with feed-hermit:source-scout --scheduled.
Flags
--scheduled: invoked by its routine (non-interactive, no operator present). The security rule restricting automated WebFetch to domains already infeed-sources.mdmeans the step-3 verification fetch cannot run — candidates are queued unverified for operator review instead of being auto-added.- No flag (default): interactive/on-demand (operator ran
/source-scout). Full behavior — verify and auto-add — since the operator's live presence satisfies the security rule's intent.
Steps
-
Read current state (in parallel):
feed-sources.md— extract active source names, URLs, categories. Count sources per category.feed-categories.md— all P1/P2 categories and their priorities.- Glob
.claude-code-hermit/compiled/story-arcs-*.md, read the most recent. Extract Watch-clause keywords from each active arc under## Active.
-
Identify gaps:
- Any P1 or P2 category with fewer than 3 active sources is a gap category.
- Active story arcs with Watch keywords that no current source covers by name/domain are arc gaps.
- No gaps → pipe
source-scout: no gaps foundinto.claude-code-hermit/bin/hermit-run task note .claude-code-hermit <id>only inside an open record's turn (otherwise skip the note) and stop.
-
Discover candidates (up to 3 total across all gaps). Use WebSearch to find RSS feeds — for a category gap, search for RSS feeds / newsletters covering that category; for an arc gap, search for feeds covering the arc's Watch keywords.
No flag (interactive): for each candidate, verify the feed URL with WebFetch (valid RSS/Atom XML). Discard any that 404 or return non-feed content.
--scheduled: do NOT WebFetch candidate URLs — they are not yet infeed-sources.md, so an automated fetch would violate the domain-allowlist rule. Collect candidates from WebSearch results as-is (name, URL, gap addressed, why it surfaced), explicitly marked unverified. Skip to step 4.
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 Changed 8348e2fc2400
- 1mo ago Changed c2512e622f35
- 2mo ago First seen · 80 lines · 77 tokens per session scan A 96e0265ef6a2
source-scout is a skill published in the GitHub repository gtapps/claude-code-hermit (83 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,250 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-09-03.
Other skills, from other repositories
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
crest-narrative
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
crest-okr
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
apex-recon
Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.
crest-recon
Strategic context reconnaissance — read existing roadmaps, OKRs, competitive docs, and briefs to establish context before planning. Use when asked to "understand our strategy", "what's the current roadmap", "what OKRs do we have", "strategic context", or before starting any prioritization or roadmap work.
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.