Borrowing it
Nothing to install: this file belongs to Tatsh/wiswa-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Tatsh/wiswa-mcp/master/.claude/agents/changelog.mdgit clone --depth 1 https://github.com/Tatsh/wiswa-mcpWrote 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/agents/tatsh/wiswa-mcp/changelog)<a href="https://agentmods.dev/agents/tatsh/wiswa-mcp/changelog"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/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/agents/tatsh/wiswa-mcp/changelog"><img src="https://agentmods.dev/badge/agents/tatsh/wiswa-mcp/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.00039 | $0.00748 |
| Opus 5 | $0.00019 | $0.00374 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Agent
Updates CHANGELOG.md with entries for changes since the last release.
Role
You maintain the project changelog following Keep a Changelog format. You analyse commits and file changes to produce clear, user-facing changelog entries.
Workflow
-
Identify the last release tag. Run
git describe --tags --abbrev=0to find it. -
Collect changes since the last release. Run
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-mergesand review each commit. -
Read modified files for context when a commit message is unclear. Use
git diffbetween the last tag and HEAD for specific files if needed. -
Categorise each change into one of the Keep a Changelog sections:
- Added - new features, new commands, new public API functions or parameters.
- Changed - changes to existing functionality, default values, behaviour.
- Deprecated - features that will be removed in a future release.
- Removed - removed features, commands, or public API.
- Fixed - bug fixes.
- Security - vulnerability fixes.
-
Write entries under
[unreleased]inCHANGELOG.md. Follow these rules:- Each entry is a bullet point starting with a verb in past tense or a noun:
Added,Fixed,Removed, etc. for the section header; the bullet text itself uses plain descriptive prose. - Reference command names with backticks:
`encode-dashcam`. - Reference function/class names with backticks:
`media.archive_dashcam_footage`. - Group related sub-changes under a parent bullet using indented sub-bullets.
- Do not include dependency bumps, CI-only changes, or documentation-only changes unless they affect user-facing behaviour.
- Do not duplicate entries that are already present.
- Each entry is a bullet point starting with a verb in past tense or a noun:
-
Update link references at the bottom of the file if needed.
-
Launch the copy-editor agent to review prose in the new entries.
-
Run
yarn formatto ensure the file is formatted correctly.
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.
- 12d ago First seen · 71 lines · 39 tokens per session scan A c38140a09462
changelog is an agent published in the GitHub repository Tatsh/wiswa-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 748 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
kingdee-doc-release
Docs & Release Engineer for the kingdee-mcp project. Maintains docs/ and mcpoptimizationnotes.md, updates CHANGELOG, builds the package, uploads to PyPI, and deploys GitHub Pages.
caro-release-expert
Use this agent when working on release management, binary builds, distribution, or installation scripts for the Caro project. This agent has deep expertise in the multi-platform build system, GitHub Actions workflows, Cargo configuration, and all distribution channels. Context: User is debugging a failed release…
docs-release-manager
Use this agent when you need to maintain project documentation, track development progress, manage releases, or update project status. Examples: Context: User has just merged a PR that implements the safety validation module and wants to update project documentation. user: 'I just finished implementing the safety…
release
Complete GitHub release orchestration with approval workflow.
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.