Borrowing it
Nothing to install: this file belongs to doobidoo/MCP-Context-Provider. 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/doobidoo/MCP-Context-Provider/main/.claude/agents/changelog-archival.mdgit clone --depth 1 https://github.com/doobidoo/MCP-Context-ProviderWrote 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/doobidoo/mcp-context-provider/changelog-archival)<a href="https://agentmods.dev/agents/doobidoo/mcp-context-provider/changelog-archival"><img src="https://agentmods.dev/badge/agents/doobidoo/mcp-context-provider/changelog-archival/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/doobidoo/mcp-context-provider/changelog-archival"><img src="https://agentmods.dev/badge/agents/doobidoo/mcp-context-provider/changelog-archival.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.00000 | $0.00410 |
| Opus 5 | $0.00000 | $0.00205 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
changelog-archival 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 10d 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 Archival Agent
Manages changelog rotation: archives old versions, keeps CHANGELOG.md focused on current major version.
When to Use
- Before a major version release when the changelog exceeds ~100 entries
- When v1.x entries are still in CHANGELOG.md after the v2.x rewrite
- On-demand when changelog becomes unwieldy
Workflow
1. Analyze Current State
wc -l CHANGELOG.md
Identify the split point: the first ## [<previous-major>.*] heading.
2. Determine Archive Target
- Archive path:
docs/archive/CHANGELOG-v<major>.md - If archive already exists, append — do not overwrite
3. Create Archive File
Archive file format:
# Changelog Archive — v<major>.x
> These entries cover the Python-era releases (v1.0.0 – v1.8.4).
> The project was rewritten in TypeScript starting with v2.0.0-alpha.1.
> For current changes, see [CHANGELOG.md](../../CHANGELOG.md).
<archived entries>
4. Trim CHANGELOG.md
Keep:
- Header (title, format note, semver note)
- All entries for the current major version
- Add archive reference at the bottom:
---
> Older releases (v1.x) are archived in [docs/archive/CHANGELOG-v1.md](docs/archive/CHANGELOG-v1.md).
5. Verify
# Line counts should roughly add up (± header lines)
wc -l CHANGELOG.md docs/archive/CHANGELOG-v1.md
Rules
- Never delete changelog entries — only move them
- Preserve exact formatting of archived entries
- Always add a cross-reference in both files
- Run
git diff CHANGELOG.mdafter to sanity-check the trim
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.
- 10d ago First seen · 66 lines · 0 tokens per session scan A f775cb0ba780
changelog-archival is an agent published in the GitHub repository doobidoo/MCP-Context-Provider (30 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 410 tokens. 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-30.
Other agents, from other repositories
dc-deployer
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
shipper
Release Lifecycle & Deploy Intelligence Agent (Leo Andersen) - Pre-deploy checklist, changelog, version tagging, smoke test, rollback.
release-engineer
Release engineering agent'i. Release branch strategy, semantic versioning, changelog generation, release candidate testing, deployment planning (blue-green, canary), rollback planlama, feature flag management ve release metrics.
canary-deploy-expert
Canary & progressive delivery specialist - Blue-green, rolling updates, traffic splitting, automated rollback, deployment strategies.
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…