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-pr-risk-reviewWrote 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-pr-risk-review)<a href="https://agentmods.dev/skills/jakyeamos/tmcp/tmcp-pr-risk-review"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-pr-risk-review/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-pr-risk-review"><img src="https://agentmods.dev/badge/skills/jakyeamos/tmcp/tmcp-pr-risk-review.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.00034 | $0.00291 |
| Opus 5.5 | $0.00014 | $0.00116 |
| Sonnet 5.5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
tmcp-pr-risk-review 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 1mo 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 PR Risk Review
Status: experimental. This workflow remains shipped and callable, but its public contract may change.
Use this skill when the user asks to review a PR, branch, diff, changed contract, merge risk, regression risk, or release risk before merging.
Do not use it as a replacement for normal code review findings; use it to structure evidence, risk, and remediation.
Workflow
- Gather evidence: PR metadata, diff summary, touched contracts, test changes, CI status, migration/docs changes, and known release constraints.
- Invoke
tmcp_explainfor the PR-risk packet. - Invoke
expert_rubric_review_planfor a scored risk and merge-readiness plan. - If MCP tools are unavailable, run from the TMCP plugin root:
node scripts/tmcp_launcher.mjs review-plan "Review PR risk and merge readiness for <project>" --project-path "<project-path>" --evidence-json '<json>' --write-artifacts
Output Contract
Produce or cite:
- Changed-surface map.
- Contract and regression risks.
- CI/test/doc evidence gaps.
- Merge blockers and warnings.
- Ordered remediation plan.
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.
- 1mo ago First seen · 35 lines · 34 tokens per session scan A 1e22e1d819fa
tmcp-pr-risk-review is a skill published in the GitHub repository jakyeamos/tmcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 291 once invoked, about $0.0001 per session on Opus 5.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
pr-description-generator
Generates comprehensive, structured PR descriptions from git diff or branch comparison. Includes summary, changelog, testing notes, and deployment considerations.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
code-review
Perform a structured code review of changes, checking for correctness, style, tests, and potential issues.
review-prs
Triage open PRs — screen from the diff, delegate the admission judgment to audit-the-list, then merge or close on GitHub. Fire when the maintainer asks to review PRs, process the PR queue, or judge whether a specific PR should be merged.