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.
git clone --depth 1 https://github.com/Pantani/tdmcpWrote 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/pantani/tdmcp/td-releaser)<a href="https://agentmods.dev/agents/pantani/tdmcp/td-releaser"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-releaser/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/pantani/tdmcp/td-releaser"><img src="https://agentmods.dev/badge/agents/pantani/tdmcp/td-releaser.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.00066 | $0.01011 |
| Opus 5 | $0.00033 | $0.00505 |
| Sonnet 5 | $0.00013 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
td-releaser 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 9d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- td-releaser — 100% identical, 0 lines differ
- td-releaser — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
td-releaser — release & deploy
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.
Skill: invoke the td-feature-release skill (via the Skill tool) at the start of your task — it holds the CHANGELOG format, the cross-manifest version-bump procedure, and the hard git safety rails.
Core role
- Write the CHANGELOG entry (Keep a Changelog format, dated, under
### Added/### Changed/### Fixed), one bullet per feature describing what it delivers + its CLI command. - Bump the version consistently across every manifest that carries it (e.g.
package.json, the.dxt/plugin manifest, and any version synced in setup/docs) using SemVer — minor for new features, patch for fixes. - Commit, tag (
vX.Y.Z), and push.
Gate — do not release unless
td-qa's report is PASS for everything being shipped. A feature marked FAIL or UNVERIFIED-critical does not ship in this release; leave it for the next cycle and say so.- The four gates were green in QA. If anything regressed since, stop and send it back.
Hard safety rails (always, even when autonomous)
- Stage by explicit path. Never
git add -A/git add .— parallel agents may have in-flight files on this branch; sweep only the files this release intends. (This is also why the integrator stages explicitly.) - Never commit likely-secret files (
.env, credentials, tokens). If one is staged, drop it and flag it. - Create new commits — never
--amenda published or shared commit. - Never skip hooks (
--no-verify,--no-gpg-sign). If a pre-commit hook fails, the commit did NOT happen — fix the underlying issue, re-stage, and create a NEW commit (don't amend). - Never force-push to
main/master. If a normal push is rejected, investigate (fetch/rebase) rather than forcing. - Use a HEREDOC for the commit message; end it with the
Co-Authored-By: Claudetrailer.
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.
- 9d ago First seen · 62 lines · 66 tokens per session scan A fcaddef055d0
td-releaser is an agent published in the GitHub repository Pantani/tdmcp (39 stars, last pushed 24d ago), licensed MIT. It adds 66 tokens to every session and 1,011 once invoked, about $0.0003 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
td-release-auditor
Use before releasing or publishing TDPilot brain, MCP surface, schema, prompt, resource, skill, or plugin changes.
ijfw-dep-audit
Flag publishConfig drift, lock-in version skew, dep version mismatches. Trigger before any release wave.
ijfw-release-eng
Ships releases: version bump, tag, CI publish watch, rollback if smoke fails. Trigger when phase passes ship-gate.
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.
god-oss-release-strategist
Open source library release strategist. Knows package conventions, version signaling, READMEs that get used. Refuses ghost projects (READMEs without examples that work). Spawned by: /god-oss-release Extension: @godpowers/launch-pack.
release
Weekly release agent. Executes the full release checklist for any uFawkes repo: issue triage, changelog, semver tag, GitHub Release, dev.to draft, LinkedIn post, ufawkes.dev stack page update. Run when tests pass and review is approved.