Borrowing it
Nothing to install: this file belongs to tomtom-international/tomtom-maps-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tomtom-international/tomtom-maps-mcp/main/.agents/skills/tomtom-mcp-pr-description/SKILL.mdgit clone --depth 1 https://github.com/tomtom-international/tomtom-maps-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/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-pr-description)<a href="https://agentmods.dev/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-pr-description"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-pr-description/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/tomtom-international/tomtom-maps-mcp/tomtom-mcp-pr-description"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-pr-description.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.00153 | $0.02995 |
| Opus 5.5 | $0.00061 | $0.01198 |
| Sonnet 5.5 | $0.00031 | $0.00599 |
| Haiku 4.5 | $0.00015 | $0.00299 |
Grade A, and why
tomtom-mcp-pr-description 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The description is the review artifact: a reviewer has to reach the solution from it without
reading the diff first. State the problem, then the shape of the answer, then walk the diff with
links. tomtom-mcp-preflight runs first and proposes the title;
this skill writes the body.
The template
Every PR fills .github/pull_request_template.md, and
keeps its four headings in order — reviewers scan for them:
## Description— the body proper; its structure is below.## Type of change— delete the options that don't apply; Breaking change ticked exactly when the title carries!andCHANGELOG.mdhas a BREAKING entry. A parenthesis may say what the docs update covers.## How Has This Been Tested?— see Tests.## Checklist:— tick only what is true; drop a line that doesn't apply rather than leave it unticked without a reason. The DCO line is ticked only when every commit carriesSigned-off-by:.
Then the attribution footer.
Inside Description
In this order; only the first two are always there.
- Top line, for a stacked PR:
Stacked on #314plus what the diff against that parent contains, and that the quality checks run only on PRs tomain, so the results below are local. The only place the stack is discussed. Docs portal, for a changeCODING_GUIDELINES.md§ 10 covers:Docs portal: <the sibling PR's link>, orDocs portal: no page affected, on a line of its own after any stack line. Only the sibling's link goes on it: the review skill fetches every docs PR that line links. - Problem — what is wrong today, who it hurts (the model, an integrator, a host), and the evidence: a live call, a count, a before/after. Open with the problem, never a verdict.
- Solution — the shape of the answer before any file is named: the mechanism and what it replaces, or the rule it enforces with its ADR. A one-file fix skips it.
- The diff, in sections (
###) — one per mechanism or area, ordered as a reviewer must read them: what the rest depends on first. Commits are kept on merge, so a section that is one commit links its heading to that commit. - Breaking changes — when the title carries
!: aWas/Is now/Whytable that agrees with the CHANGELOG's BREAKING entries. - Screenshots — when an MCP app changes visually.
- Open items — a gap this PR still means to close.
### Caveats— see Caveats.### Follow-ups— only the author's own plan beyond this PR.
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.
- 6d ago Changed bb05d883395b
- 10d ago Changed · +5 lines 77a9316764d7
- 16d ago First seen · 207 lines · 153 tokens per session scan A 062313a5ba18
tomtom-mcp-pr-description is a skill published in the GitHub repository tomtom-international/tomtom-maps-mcp (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 153 tokens to every session and 2,995 once invoked, about $0.0006 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-10-13.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…