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-healthgit 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-health)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/source-health"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/source-health.svg" alt="Measured on agentmods" 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.00071 | $0.01453 |
| Opus 5 | $0.00036 | $0.00727 |
| Sonnet 5 | $0.00014 | $0.00291 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
source-health 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Health
Read-only audit of brief source performance. Scans recent briefs and flags underperforming sources before they silently waste fetch budget.
When to use
- Manually, to spot-check source health.
- Wired into weekly review to catch slow-building problems.
- After adding a new source, to confirm it's yielding items.
Steps
-
Read
feed-sources.md— extract the active source names (Name column). -
Glob briefs — list
.claude-code-hermit/briefs/*.md, sort descending by filename (newest first), take the last N = 10 (override with--last N). -
Parse each brief's frontmatter — extract:
sources_used: sources that contributed ≥1 item.sources_skipped: sources that failed to fetch (network error, Chrome unavailable, script error).sources_quiet: sources that fetched cleanly but yielded 0 items.fetch_log: per-source efficiency array (may be absent in older briefs — treat as missing, not an error).
If a source appears in none of the three arrays, mark it
unknownfor that brief (may predate the schema). -
Compute per-source streaks — walking newest→oldest for each active source:
consecutive_quiet: consecutive briefs the source was insources_quiet.consecutive_skipped: consecutive briefs the source was insources_skipped.- Reset the streak when the source appears in
sources_usedor isunknown.
-
Flag threshold violations — any source where
consecutive_quiet >= 3ORconsecutive_skipped >= 3. -
Output a health table:
## Source Health — YYYY-MM-DD (last 10 briefs) | Source | Last 10 (newest→oldest) | Streak | Status | |-----------------------|----------------------------|--------------|-----------| | Source A | ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ | — | healthy | | Source B | ~ ~ ~ ✓ ~ ~ ~ ✓ ~ ~ | 3 quiet | ⚠ warn | | Source C | ✗ ✗ ✗ ✗ ✓ — — — — — | 4 skipped | ✗ flag |Legend:
✓contributed ·~quiet (fetched, nothing relevant) ·✗skipped (fetch failed) ·—not yet in sources or brief predates schema.
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 First seen · 110 lines · 71 tokens per session scan A 952918e46d88
source-health is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,453 once invoked, about $0.0004 per session on Opus 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
cco-tools
Show what tools actually cost in tokens — learned per-tool averages from observed results, replacing the hardcoded MCP/Agent guesses.
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…
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.
magic-compact
Compact this Claude Code session.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
subagent-output-templating
Template for structured sub-agent output including YAML log format, task completion reports (WHY/WHAT/TRADE-OFFS/RISKS), and summary constraints. Use when defining how sub-agents should report results.