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 add-sourcegit 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/add-source)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/add-source"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/add-source/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/add-source"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/add-source.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.00056 | $0.00521 |
| Opus 5.5 | $0.00022 | $0.00208 |
| Sonnet 5.5 | $0.00011 | $0.00104 |
| Haiku 4.5 | $0.00006 | $0.00052 |
Grade A, and why
add-source 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-source — 92% identical, 4 lines differ
What it actually says
Add Source
Add a new entry to feed-sources.md, enforcing the correct table format and source type.
Steps
-
Collect inputs — ask the operator for:
- Name: short display name (e.g. "The Daily Dispatch").
- URL: full URL to the source.
- Category: must match one of the categories in
feed-categories.md— read that file first and present the options. - Type (optional — infer if not provided):
- URL contains
reddit.com→reddit - URL contains
twitter.comorx.com→x - URL ends in
.rss,.atom, or/feed→rss - URL is a known WebFetch blocker (a domain that blocks server-side fetch and requires a browser) →
chrome - Otherwise →
web
- URL contains
- Notes (optional): brief description of what the source covers.
-
Validate:
- URL must start with
https://. - Name must not already exist in
feed-sources.md— read the file and check. - Category must match an existing category from
feed-categories.md.
- URL must start with
-
Read
feed-sources.mdto confirm the current table structure, then append the new row under## Active Sources:| {Name} | {URL} | {Category} | {Type} | {Notes} |Align columns with the existing table width. Insert alphabetically by Name within the same category, or at the end if unsure.
-
Confirm — show the operator the new row before writing. Write only after confirmation.
-
Note in task: inside an open record's turn, pipe the following into
.claude-code-hermit/bin/hermit-run task note .claude-code-hermit <id>; otherwise skip the note:[HH:MM] Added source: {Name} ({Type}) to {Category}. -
Mention in next brief — new source additions are mentioned automatically in the next brief (no action needed here).
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 631db3c367a4
- 2mo ago First seen · 43 lines · 56 tokens per session scan A eebb365458be
add-source is a skill published in the GitHub repository gtapps/claude-code-hermit (83 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 521 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-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.