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 agentmods add skills/gtapps/claude-code-hermit/pipeline-digestnpx skills add gtapps/claude-code-hermit --skill pipeline-digestgit 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/pipeline-digest)<a href="https://agentmods.dev/skills/gtapps/claude-code-hermit/pipeline-digest"><img src="https://agentmods.dev/badge/skills/gtapps/claude-code-hermit/pipeline-digest.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.00099 | $0.00667 |
| Opus 5 | $0.00049 | $0.00333 |
| Sonnet 5 | $0.00020 | $0.00133 |
| Haiku 4.5 | $0.00010 | $0.00067 |
Grade A, and why
pipeline-digest 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 6d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Digest
Delta-gated wrapper over the pipeline facts /release-status reports in full. A quiet day costs one script call and sends nothing.
Steps
1. Collect
bun .agents/skills/pipeline-digest/scripts/digest.ts .claude-code-hermit
Run from the repo root. Two possible outputs:
NOCHANGE— the pipeline is exactly where it was last time. Say so in one line and stop. Do not send anything.CHANGED|<hash>followed by the digest body — continue.
2. Report and notify
Print the digest body in the conversation. Then send it to the operator:
.claude-code-hermit/bin/hermit-run channel-send .claude-code-hermit --notice
with {"maintainer": "<the digest, channel-voiced>"} on stdin. The hermit-run dispatcher resolves the installed plugin itself — do not try to derive a plugin root from this skill's Base directory, which points at .agents/, not the plugin.
Channel voice: plain language, no file paths, no slash commands, no cron strings. Plugin names and versions are fine — the maintainer chat is the technical audience. Lead with what the operator can act on.
3. Commit the hash
bun .agents/skills/pipeline-digest/scripts/digest.ts .claude-code-hermit commit <hash>
Commit only when the digest reached the operator, or when there was nobody to send it to. Read the JSON on stdout — the exit code alone is not enough, because the script exits 1 whenever delivered is false, no_channel included:
| Send result | Action |
|---|---|
"delivered":true (exit 0) |
commit the hash |
"no_channel":true (exit 1), no channel enabled in config.json |
commit the hash — there is no audience, so printing it was the delivery |
"no_channel":true (exit 1), but a channel is enabled |
do not commit — the channel is configured and unreachable, which is a delivery failure, not an empty audience |
| exit 1 otherwise (undelivered or degraded) | do not commit, so the digest re-fires next run; report the failure per § Operator Notification |
| exit 2 (payload rejected) | do not commit; the payload is malformed — fix and retry |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 52 lines · 99 tokens per session scan A eca710b6c79a
pipeline-digest is a skill published in the GitHub repository gtapps/claude-code-hermit (74 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 667 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-08-30.
Other skills, from other repositories
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (a repo with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator that runs on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever a VERSION file…
ratchet-ship
Release runbook that takes verified local work to a green deploy — full local preflight, diff and secret review, push per the repo's convention, watch CI to completion, run the smoke checklist, and leave rollback notes. Use when the user says "ship it", "ratchet ship", "release", or after /ratchet-loop finishes a…
ship
현재 브랜치의 변경사항을 commit → push → PR 생성 → merge → 브랜치 정리까지 한 번에 처리한다. develop 브랜치가 있으면 git-flow(feature→develop→main), 없으면 GitHub Flow(feature→main)로 자동 적응하고, 머지 전 기능 게이트+보안 스캔+DB 검토+민감파일 차단을 실행한다. '/ship', 'ship', '배포해줘', '커밋하고 머지까지' 등 언급 시 호출.