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/samaxbytez/freeagent-mcp/releasegit clone --depth 1 https://github.com/samaxbytez/freeagent-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/samaxbytez/freeagent-mcp/release)<a href="https://agentmods.dev/commands/samaxbytez/freeagent-mcp/release"><img src="https://agentmods.dev/badge/commands/samaxbytez/freeagent-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.00017 | $0.00122 |
| Opus 5 | $0.00009 | $0.00061 |
| Sonnet 5 | $0.00003 | $0.00024 |
| Haiku 4.5 | $0.00002 | $0.00012 |
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
Author the release PR locally — the same outcome as the automated
release-agent.yml, for when you want to drive it by hand.
Read RELEASING.md and follow the "Release procedure (single source of
truth)" section exactly — it is authoritative for deciding the semver bump and
authoring the PR. This opens/updates a PR; per that section, never run
npm publish, never create a tag, and never push to main.
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 · 12 lines · 17 tokens per session scan A 6d5d75a60deb
release is a command published in the GitHub repository samaxbytez/freeagent-mcp (4 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 122 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 commands, from other repositories
release
Create a new Remarc release using the automated GitHub Actions workflow.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
release
Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.
release
Command "release" from khuynh22/mcp-wireshark, covering how it works, what to tell the user, if no label is added and manual fallback.
ship
Prepare a release — does not publish.
release
make a new release of the Yandex Wiki MCP project.