Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gtapps/claude-code-hermit/plugin install feed-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/feed-brief)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/feed-brief"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/feed-brief.svg" alt="Measured on agentmods" 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.00104 | $0.03213 |
| Opus 5 | $0.00052 | $0.01606 |
| Sonnet 5 | $0.00021 | $0.00643 |
| Haiku 4.5 | $0.00010 | $0.00321 |
Grade A, and why
feed-brief 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 yesterday.
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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feed Brief
Run the full 7-phase brief pipeline for this project. Config lives at the project root
(feed-sources.md, feed-categories.md, FEEDS.md); state and archive live under .claude-code-hermit/.
Flags
--morning: slotmorning. Forward-looking. Emphasize what's new since yesterday evening, what's worth opening today, emerging patterns. Tone: calm, sharp, selective.--evening: slotevening. Backward-looking. Emphasize what changed during the day, what escalated or faded, what to carry into tomorrow. Tone: slightly more reflective.--slot <name>: custom slot label (e.g.midday). Use<name>verbatim wherever<slot>appears below. Orientation defaults to the morning (forward-looking) framing unless the operator'sFEEDS.mdsays otherwise.
Resolve <slot> from the flag before starting. All filenames below use that resolved value.
Steps
- Read
FEEDS.md— brief philosophy, scoring rules, output format, and section guidance. - Read
feed-sources.md— full source list with types and URLs. - Read
feed-categories.md— operator's current focus areas and priority tiers (P1/P2). - Read
.claude-code-hermit/config.json— thefeed.enrichments.*andfeed.reaction_feedbackgates consulted in Phases 3 and 5b. A gate runs only when its value istrue; treat an absent key as disabled.
Phase 1 — Web/RSS sources
Dispatch the @feed-hermit:source-fetcher subagent (model: haiku) to fetch all web and rss
sources from feed-sources.md. Pass the full source list (URLs + names), the resolved <slot>, and the absolute project root and output path.
Output-path contract: the agent writes its extracted items to tmp/feed-source-items-<slot>.json
in the project root (never /tmp/). Pass <absolute-project-root>/tmp/feed-source-items-<slot>.json to the agent so its inherited working directory cannot redirect the write. Items are nested under sources[], each item:
{title, summary, url, published_at, source, section, author}. No scoring —
extraction only. After the agent returns, read that file for the collected items.
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.
- yesterday Changed 3e29f45d2b45
- 3d ago First seen · 216 lines · 104 tokens per session scan A 9a8be9c377e2
feed-brief is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 3,213 once invoked, about $0.0005 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-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Claude 5 lineup, Opus 5 default fallback, full 1M context at standard price).
cco-clean
Clean up old tracking data and reset statistics.
ccc-resume-session
Load the last saved session file from /.claude/sessions/ and orient fully before doing any work. Reads the complete file, formats a structured briefing (project,…
ccc-spawn
Click-first spawn hub — spin isolated work into its own session on demand: a spawntask chip in Cowork, a /spawn peer in the CLI. Also routes to $ccc-fleet or $ccc-relay.
scout-consolidation
Launch a Scout consolidation session as a background process. Runs a lighter delta scan — captures what changed since the last run and updates action items and KB.
scout-briefing
Launch a Scout morning briefing session as a background process. Auto-detects mode (morning briefing, consolidation, or weekend briefing) from the current time and day.