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.
git clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kitWrote 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/commands/cwoodruff/dotnet-claude-code-kit/changelog)<a href="https://agentmods.dev/commands/cwoodruff/dotnet-claude-code-kit/changelog"><img src="https://agentmods.dev/badge/commands/cwoodruff/dotnet-claude-code-kit/changelog/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cwoodruff/dotnet-claude-code-kit/changelog"><img src="https://agentmods.dev/badge/commands/cwoodruff/dotnet-claude-code-kit/changelog.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00210 |
| Opus 5.5 | $0.00004 | $0.00084 |
| Sonnet 5.5 | $0.00002 | $0.00042 |
| Haiku 4.5 | $0.00001 | $0.00021 |
Grade A, and why
changelog 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 1mo 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.
This is a copy
100% identical to changelog — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Update the changelog covering commits since $ARGUMENTS (default: the latest tag; if no tags, the last 30 commits).
git log <ref>..HEAD --pretty=format:'%h %s'and group by Conventional Commit type.- Render Keep-a-Changelog style sections: Added (feat), Fixed (fix), Changed (refactor/perf), Documentation (docs). Skip chore/test noise unless user-visible.
- Rewrite each entry for a user of the API — behavior and impact, not internal file names. Merge related commits into one entry.
- Call out breaking changes and new EF migrations in a ⚠ Upgrade notes block.
- Prepend the new section to CHANGELOG.md under an Unreleased heading (create the file with a standard header if missing). Show me the section before writing.
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.
- 1mo ago First seen · 13 lines · 9 tokens per session scan A b0835a760aff
changelog is a command published in the GitHub repository cwoodruff/dotnet-claude-code-kit (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 210 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to changelog, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.