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/systemartis/readmedaddy/demonpx skills add Systemartis/readmedaddy --skill demogit clone --depth 1 https://github.com/Systemartis/readmedaddyWrote 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/systemartis/readmedaddy/demo)<a href="https://agentmods.dev/skills/systemartis/readmedaddy/demo"><img src="https://agentmods.dev/badge/skills/systemartis/readmedaddy/demo.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 | $0.00096 | $0.00433 |
| Opus 5 | $0.00048 | $0.00217 |
| Sonnet 5 | $0.00019 | $0.00087 |
| Haiku 4.5 | $0.00010 | $0.00043 |
Grade A, and why
changelog-scribe 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 5d 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.
What it actually says
changelog-scribe
changelog-scribe turns the commit range since the last release tag into a clean, grouped CHANGELOG section: features, fixes, and breaking changes, each as a reader-facing line rather than a raw commit subject. It follows Keep a Changelog ordering and never invents an entry that has no commit behind it.
Method
- Find the range. Resolve the latest release tag and collect commits from
that tag to
HEAD. If there is no tag, use the full history and say so. - Classify each commit. Bucket into Added / Changed / Fixed / Removed / Deprecated / Security from the commit type and body, dropping noise commits (merges, formatting-only, CI tweaks).
- Rewrite for readers. Convert each kept commit into a present-tense, user- facing line. A commit subject is a developer note; a changelog line is for the person upgrading.
- Assemble the section. Emit a dated
## [version]block in the repo's existing changelog order, breaking changes first and called out explicitly. - Verify. Every line traces back to a real commit in the range. Nothing is added that the diff does not support.
What's in references/
references/grouping.md— the commit-type to changelog-section mapping and the noise-commit filter rules.
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.
- 5d ago First seen · 41 lines · 96 tokens per session scan A 93e9b704979d
changelog-scribe is a skill published in the GitHub repository Systemartis/readmedaddy (8 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 433 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-31.
Other skills, from other repositories
release
Publishing a jMunch release (jcodemunch-mcp, jdocmunch-mcp, jdatamunch-mcp, jragmunch-cli), reviewing/merging/closing PRs, and responding to the community. Load before any version bump, PyPI upload, tag, GitHub release, MCP registry publish, or PR merge.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…
release-preview
Cut an AgentOS release-preview. Use when the user asks for a preview, release-preview, or a branch dist-tag build.
release
Cut an AgentOS release via the scripts/publish flow. Use when the user asks to release, publish, cut a release, or bump the AgentOS version.