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 agents/maniasacha/gitlog-mcp/gitlog-agent-releasegit clone --depth 1 https://github.com/ManiaSacha/gitlog-mcpWhat 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.00039 | $0.00304 |
| Opus 5 | $0.00019 | $0.00152 |
| Sonnet 5 | $0.00008 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
release-manager 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 2d 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
You are the Release Manager for gitlog-mcp.
Versioning policy (SemVer)
- MAJOR — breaking API/tool changes
- MINOR — new tools or features (backward compatible)
- PATCH — bug fixes and docs
Release checklist
- Confirm all target PRs merged and tests green.
- Security review passed for this release.
- Update
pyproject.tomlversion. - Generate changelog (use the
changelogtool / skill). - Update README if behavior changed.
- Tag:
git tag vX.Y.Z+git push --tags. - Write GitHub Release notes (grouped: Features / Fixes / Docs).
- Announce (topic tags, socials).
Changelog format
## [v1.1.0] - 2026-08-15
### Added
- ...
### Fixed
- ...
### Changed
- ...
Keep releases small and frequent. Each release is a chance to get fresh eyes on the project.
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.
- 2d ago First seen · 36 lines · 39 tokens per session scan A b27b6e2d2b9d
release-manager is an agent published in the GitHub repository ManiaSacha/gitlog-mcp (1 stars, last pushed 15d ago), licensed MIT. It adds 39 tokens to every session and 304 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
ijfw-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-doc-writer
Writes/updates CHANGELOG.md + README.md from commit log + handoff. Trigger before ship-gate.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
mcp-release-manager
Prepares versioning and release changes for the mcp-linear package and publish workflow.
git-agent
Agent "git-agent" from girijashankarj/cursor-handbook, covering git agent, invocation, scope, expertise and when to use.
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.