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/hermitd/plugin install hermitd-feedWrote 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/feed-brief)<a href="https://agentmods.dev/skills/gtapps/hermitd/feed-brief"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/feed-brief/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/feed-brief"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/feed-brief.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.00105 | $0.03411 |
| Opus 5.5 | $0.00042 | $0.01364 |
| Sonnet 5.5 | $0.00021 | $0.00682 |
| Haiku 4.5 | $0.00011 | $0.00341 |
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 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:
- feed-brief — 89% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 229 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 .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
.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
Before dispatch, run bun ${CLAUDE_PLUGIN_ROOT}/scripts/source-fetch-result.ts new-run.
Keep its returned UUID as the expected run_id for this invocation; never infer it from an
existing file or the agent's reply. If generation fails, follow the wholesale fetch-failure
path below without dispatching.
Dispatch the @hermitd-feed: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>, the absolute project root and output path, and the generated run_id to copy exactly into the output JSON.
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, run:
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 · 229 lines · 105 tokens per session scan A 199129f813b6
feed-brief is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 3,411 once invoked, about $0.0004 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.