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 agents/murmur-io/murmur/release-engineergit clone --depth 1 https://github.com/murmur-io/murmurWhat 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 | $0.00036 | $0.00299 |
| Opus 5 | $0.00018 | $0.00150 |
| Sonnet 5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
release-engineer 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 2d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 2d ago First seen · 23 lines · 36 tokens per session scan A 1c6a940d9456
release-engineer is an agent published in the GitHub repository murmur-io/murmur (8 stars, last pushed 2d ago), licensed AGPL-3.0. It adds 36 tokens to every session and 299 once invoked, about $0.0002 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-31.
Other agents, from other repositories
collaboration
How coding agents (Claude Code, Codex, or any future harness) collaborate on this repo: who orchestrates, who implements, who reviews, and what each layer may touch. This is the map; the skills own the mechanics — never restate a skill's commands here or anywhere else (single owner per fact).
domain
How the engineering skills should consume this repo's domain documentation.
issue-tracker
Issues for this repo live on the Open Software platform (os-platform), org june — NOT GitHub Issues. GitHub Issues exist on the repo but are a legacy/watchdog surface, not the triage queue.
triage-labels
The skills speak in terms of five canonical triage roles. os-platform Issues have both statuses and labels; this repo maps roles across both axes.
demo-agents
We need a steady flow of demo videos — X/Twitter, Reddit, YouTube Shorts, blog posts, App Store-style screen recordings — and we'd like to scale that without scheduling Daniel to record every clip by hand. This doc maps the content-creation agent landscape, names the gap between "synthetic video hype" and "scripted…
qa-agents
Every quarter someone pitches an "AI does QA" tool. Most are web-first or mobile-first. MacParakeet is a menu-bar macOS app with a non-activating KeylessPanel overlay, global dictation hotkeys, and TCC-gated microphone/screen-recording flows. The general AI-QA frontier doesn't speak our shape yet. This doc tracks…