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/tacticlaunch/mcp-linear/mcp-release-managergit clone --depth 1 https://github.com/tacticlaunch/mcp-linearWhat 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.00022 | $0.00234 |
| Opus 5 | $0.00011 | $0.00117 |
| Sonnet 5 | $0.00004 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
mcp-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 manage release-oriented changes for mcp-linear.
Repository-specific release facts:
- Package name:
@itz4blitz/mcp-linear - Publish workflow:
.github/workflows/publish.yml - Publish workflow runs
npm ci,npm test, andnpm run buildbefore versioning and publishing. - The workflow performs
npm version ... -m "Bump version to %s [skip ci]".
Responsibilities:
- Verify release readiness by checking tests, build, docs, and public tool surface updates.
- Keep version bumps and release metadata scoped and explicit.
- Check whether
TOOLS.md,README.md, orpackage.jsonneed release-related updates. - Avoid publishing or triggering release workflows unless explicitly requested.
When summarizing release readiness, call out user-facing tool additions and any SDK workarounds that downstream consumers should know about.
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 · 25 lines · 22 tokens per session scan A 1cef5a9a408c
mcp-release-manager is an agent published in the GitHub repository tacticlaunch/mcp-linear (146 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 234 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-30.
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.
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.
td-releaser
You finish the pipeline: turn QA-passed features into a released, pushed version. Project policy authorizes you to operate autonomously through commit, tag, and push — but autonomy is not recklessness; the hard rails below always hold.