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/migmcc/agent-skill-quality-gate/good-skillnpx skills add migmcc/agent-skill-quality-gate --skill good-skillgit clone --depth 1 https://github.com/migmcc/agent-skill-quality-gateWrote 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/migmcc/agent-skill-quality-gate/good-skill)<a href="https://agentmods.dev/skills/migmcc/agent-skill-quality-gate/good-skill"><img src="https://agentmods.dev/badge/skills/migmcc/agent-skill-quality-gate/good-skill.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.00026 | $0.00357 |
| Opus 5 | $0.00013 | $0.00179 |
| Sonnet 5 | $0.00005 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
changelog-writer 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-writer
Purpose
Generate a clear, human-readable changelog entry for a release from a list of merged pull requests, grouped by change type (features, fixes, docs).
When to use
Use this skill when preparing a release and you have a list of merged PRs that need to be summarized into release notes. Do not use it to decide version numbers — that is the release-manager's job.
Inputs
- A list of merged pull request titles and numbers.
- The target release version (e.g.
1.4.0).
Outputs
- A Markdown changelog section with the version header and grouped bullet
points, ready to paste into
CHANGELOG.md.
Acceptance criteria
- Every input PR appears exactly once in the output.
- Entries are grouped under Features, Fixes and Docs headings.
- The version header matches the provided version.
Examples
Input: PRs #12 Add export button (feature), #13 Fix crash on empty list (fix).
Output:
## 1.4.0
### Features
- Add export button (#12)
### Fixes
- Fix crash on empty list (#13)
Limitations
- Does not infer change type when a PR is untagged; it asks for clarification.
- English output only in v0.1.
Test cases
- TC-1: three PRs across all groups produce three grouped sections.
- TC-2: an untagged PR triggers a clarification request rather than a guess.
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 · 57 lines · 26 tokens per session scan A 0cf118a87181
changelog-writer is a skill published in the GitHub repository migmcc/agent-skill-quality-gate (2 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 357 once invoked, about $0.0001 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
squad-version-check
Internals of how @bradygaster/squad-cli stamps its version, how squad upgrade works (what it preserves vs overwrites), and how to probe the npm registry for the latest version from a coordinator prompt.
versioning-policy
Semver versioning rules for Squad SDK and CLI — prevents prerelease version incidents.
awf-release-integrator
Upgrade gh-aw to latest gh-aw-firewall release and identify follow-up spec tasks.
release-version
Steps to cut a VNote version release (e.g. v4.3.0) — bump the version with scripts/updateversion.py, refresh and fill zhCN/ja translations via lupdate, write the changes.md changelog, and trigger the CI [Release] build. Use when asked to "release", "cut a release", "bump the version", or "prepare vX.Y.Z".
release-process
Pre-release validation, npm publish procedures, and post-publish verification.
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.