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 commands/mediagraph-io/mediagraph-mcp/releasegit clone --depth 1 https://github.com/mediagraph-io/mediagraph-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/commands/mediagraph-io/mediagraph-mcp/release)<a href="https://agentmods.dev/commands/mediagraph-io/mediagraph-mcp/release"><img src="https://agentmods.dev/badge/commands/mediagraph-io/mediagraph-mcp/release.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 | $0.00000 | $0.00405 |
| Opus 5 | $0.00000 | $0.00202 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
release 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 3d 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
/release
Release a new version of the package to npm and GitHub.
Usage
/release <otp>
/release <version> <otp>
otp: Required - npm one-time password for publishingversion: The version to release (e.g.,patch,minor,major)- If not provided, defaults to
patch
- If not provided, defaults to
Examples:
/release 123456- patch release with OTP/release minor 123456- minor release with OTP
Steps
-
Check for uncommitted changes and commit them if any exist:
git status --porcelainIf there are changes, stage, commit, and push them before proceeding:
git add -A git commit -m "<descriptive message of the changes>" git push -
Run the release script with the provided arguments:
./scripts/release.sh [version] <otp> -
Wait for GitHub Actions to build the .mcpb and create the release:
gh run watch --repo mediagraph-io/mediagraph-mcp -
Report the release URLs:
- npm: https://www.npmjs.com/package/@mediagraph/cli
- GitHub Release: https://github.com/mediagraph-io/mediagraph-mcp/releases
- URL of the MCPB download: https://github.com/mediagraph-io/mediagraph-mcp/releases/download/v/mediagraph-mcp.mcpb
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.
- 3d ago First seen · 57 lines · 0 tokens per session scan A 1928ab71f901
release is a command published in the GitHub repository mediagraph-io/mediagraph-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 405 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-31.
Other commands, from other repositories
changelog
Generate a new changelog entry by reading all changeset files and creating a properly formatted entry in .changelog/v3.mdx.
merge-and-status
Merge the current PR, pull main, surface any open contributor PRs and untriaged contributor issues, and show open milestone issues.
ship
Deliver the increment. Then go live with a rollback you have run.
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
release-tag
Create and push a version tag after a release PR has been merged.
release
Orchestrate a complete release workflow with quality gates, version bumping, and publishing automation.