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/xyiqq/skilldoctor/release-notesnpx skills add xyiqq/skilldoctor --skill release-notesgit clone --depth 1 https://github.com/xyiqq/skilldoctorWrote 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/xyiqq/skilldoctor/release-notes)<a href="https://agentmods.dev/skills/xyiqq/skilldoctor/release-notes"><img src="https://agentmods.dev/badge/skills/xyiqq/skilldoctor/release-notes.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.00037 | $0.00146 |
| Opus 5 | $0.00018 | $0.00073 |
| Sonnet 5 | $0.00007 | $0.00029 |
| Haiku 4.5 | $0.00004 | $0.00015 |
Grade A, and why
release-notes 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
Release Notes
Quick start
- Read recent commits or merged pull requests.
- Group changes into Added, Changed, Fixed, and Security.
- Write short bullets that explain why the change matters.
Output
## Added
- ...
## Fixed
- ...
Keep the summary under 20 bullets. Do not invent changes that are not in the history.
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 · 29 lines · 37 tokens per session scan A 9e5232ffa874
release-notes is a skill published in the GitHub repository xyiqq/skilldoctor (11 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 146 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 skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
changeset
Use this skill when a Biome change may affect users and you must decide whether it needs a changeset, choose the release level, or create and edit .changeset/.md release-note text. Do not use for implementation details or PR descriptions.
release-swift
Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes. Use to ship an Early Access beta or a stable release.
remotion-best-practices
Best practices for Remotion - Video creation in React.
ultracite
Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…
finishing-a-development-branch
当实现完成、所有测试通过、需要决定如何集成这份工作时使用.