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/ryanmichaeljames/dataverse-mcp/changelognpx skills add ryanmichaeljames/dataverse-mcp --skill changeloggit clone --depth 1 https://github.com/ryanmichaeljames/dataverse-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/skills/ryanmichaeljames/dataverse-mcp/changelog)<a href="https://agentmods.dev/skills/ryanmichaeljames/dataverse-mcp/changelog"><img src="https://agentmods.dev/badge/skills/ryanmichaeljames/dataverse-mcp/changelog.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.00012 | $0.00506 |
| Opus 5 | $0.00006 | $0.00253 |
| Sonnet 5 | $0.00002 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00051 |
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 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
Changelog - Keep a Changelog v1.1.0
Update CHANGELOG.md with entries for the current changes. Always write under ## [Unreleased].
Categories
Use only what applies — omit the rest:
- Added — new tools or new options on existing tools
- Changed — changed behavior of existing tools
- Fixed — bug fixes
- Removed — tools or options removed
- Security — security fixes
Entry rules
- One bullet per logical change, not per file or function
- Name the tool in backticks:
`dataverse_list_tables` - Describe what it does for the user, not how it's implemented
- Omit HTTP internals, refactors, dependency bumps, and test changes
- Keep each bullet to one sentence — enough to understand the impact
What to skip
Do not add entries for:
- Internal refactors with no user-visible effect
- Dependency version bumps
- Code style or formatting changes
- Test additions or changes
- Documentation-only changes
Example
## [Unreleased]
### Added
- `dataverse_get_foo` tool to retrieve foo records by ID
### Security
- `dataverse_delete_bar` now requires `DATAVERSE_ALLOW_DELETE=true` to prevent accidental deletions
## [1.2.0] - 2026-05-01
### Added
- `dataverse_list_bars` tool to list bar records with optional status filter
### Changed
- `dataverse_get_foo` now returns `displayname` in addition to `id`
### Fixed
- `dataverse_list_foos` no longer returns duplicate entries when a filter is applied
### Removed
- `dataverse_legacy_query` tool removed; use `dataverse_query_table` instead
## [1.1.0] - 2026-04-01
### Added
- `dataverse_query_table` tool to query records with OData filter and column selection
Steps
- Read
CHANGELOG.md - Review the diff or description of changes
- Identify the correct categories and write concise bullets
- Insert them under
## [Unreleased], creating category headers as needed - Do not modify any released version sections
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 · 76 lines · 12 tokens per session scan A 4d839937b660
changelog is a skill published in the GitHub repository ryanmichaeljames/dataverse-mcp (2 stars, last pushed 12d ago), licensed MIT. It adds 12 tokens to every session and 506 once invoked, about $0.0001 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…