Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jakyeamos/tmcpnpx agentmods add skills/jakyeamos/tmcp/tmcp-release-readinessWrote 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/jakyeamos/tmcp/tmcp-release-readiness)<a href="https://agentmods.dev/skills/jakyeamos/tmcp/tmcp-release-readiness"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-release-readiness/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/skills/jakyeamos/tmcp/tmcp-release-readiness"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-release-readiness.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.00033 | $0.00347 |
| Opus 5 | $0.00016 | $0.00173 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
tmcp-release-readiness 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 11d 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
TMCP Release Readiness
Use this skill when the user asks whether a repo, branch, feature, sprint, milestone, or product is ready to ship, merge, release, or hand off. Also use it for quality ladder gap analysis, launch-blocker triage, release-readiness planning, and ordered remediation before implementation.
Do not use it for normal test failures or active debugging unless the user asks for a release rubric or remediation plan.
Workflow
- Gather evidence from project instructions, README, CI config, tests, build scripts, release docs, current git status, and recent quality-tool output.
- Invoke TMCP through MCP tools when exposed:
tmcp_explainfor the release-readiness packet.expert_rubric_review_planfor the scored rubric and remediation plan.
- If MCP tools are not exposed, use the CLI from the TMCP plugin root:
node scripts/tmcp_launcher.mjs review-plan "Review release readiness for <project>" --project-path "<project-path>" --evidence-json '<json>' --write-artifacts
- Treat missing evidence as a finding, not as permission to assume readiness.
- Stop at the plan unless the user explicitly asks for implementation.
Output Contract
Produce or cite:
- TMCP packet and
substance_check. - Scored release-readiness rubric.
- Evidence-backed ship blockers, risks, and gaps.
- Ordered remediation slices with verification expectations.
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.
- 11d ago First seen · 36 lines · 33 tokens per session scan A 54d435ed0f55
tmcp-release-readiness is a skill published in the GitHub repository jakyeamos/tmcp (0 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 347 once invoked, about $0.0002 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
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
cli-release
Release and recover first-party Composio CLI binaries through Build CLI Binaries, including automatic beta builds, promote-stable dispatches, beta-tag selection, asset and installation verification, and failed release recovery. Use when a contributor asks to build a CLI beta, publish or promote a stable CLI version…
config-loading-precedence
How Xberg resolves configuration — CLI-mode and server/MCP-mode precedence orders, config file auto-discovery (xberg.toml walk-up, then the user config dir), field-level inline JSON merge (mergejsonintoconfig), the ExtractionOverrides CLI layer, and the two mechanisms that make a config change silently do nothing.…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-versioning
How xberg versions are synced and released — Cargo.toml is the single source of truth, task version:sync propagates it to alef-managed binding manifests AND the integrations under integrations/, which are versioned and published in lockstep with core (including -rc.N). Load before bumping a version, editing the…