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-docs-update-pr/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-docs-update-pr)<a href="https://agentmods.dev/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-docs-update-pr"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-docs-update-pr/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-docs-update-pr"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-docs-update-pr.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.00173 | $0.02390 |
| Opus 5.5 | $0.00069 | $0.00956 |
| Sonnet 5.5 | $0.00035 | $0.00478 |
| Haiku 4.5 | $0.00017 | $0.00239 |
Grade C, and why
tomtom-mcp-docs-update-pr scanned grade C with 1 finding 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules/.cache/devportal-documentation How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keep the docs portal's MCP pages
consistent with the server. CODING_GUIDELINES.md § 10 holds the rules —
which changes owe a sibling PR, its branch and timing, the end-state voice; this skill applies them. Its
output is always a draft PR in tomtom-internal/devportal-documentation: the skill writes prose, and
that PR's review is where a person judges it.
| Invoked | Mode | Source of truth | Scope |
|---|---|---|---|
by tomtom-mcp-preflight, or "update the docs for my change" |
diff | the branch head | what the diff touches |
| "audit the docs", "are the MCP docs up to date" | audit | the latest release tag | every page, every surface |
Audit mode reads the release, not main: the pages describe the server readers connect to, and an
unreleased change gets its pages through its own sibling PR.
The commands are POSIX shell. Run each gh and git push in a shell call of its own, as
.claude/settings.json exempts only calls that start with them from Claude Code's sandbox.
Step 1: Clone the pages
Pick the sibling branch first — tomtom-maps-mcp/<this branch> in diff mode,
tomtom-maps-mcp/sync-<tag> in audit mode — and look for its open PR:
gh pr list -R tomtom-internal/devportal-documentation --head tomtom-maps-mcp/<branch> --json number,url
Clone fresh — sparse and shallow, a few seconds, into the gitignored cache — from that branch when its PR
exists, so the skill updates the PR rather than opening a second; from develop otherwise. --depth 1
fetches that one branch only, so pick it here:
rm -rf node_modules/.cache/devportal-documentation
gh repo clone tomtom-internal/devportal-documentation node_modules/.cache/devportal-documentation -- --depth 1 --branch <develop, or the sibling branch> --filter=blob:none --sparse
git -C node_modules/.cache/devportal-documentation sparse-checkout set documentation/tomtom-maps-mcp
When an open docs PR already rewrites the pages this run edits, clone its branch instead and stack the
sibling on it, so the two don't conflict. Say so on the sibling's top line, and retarget it to develop
once that PR merges.
A gh 404 means no access. Stop and report "not checked: no access to devportal-documentation; the
maintainer opens the sibling PR" — it blocks nothing.
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.
- 10d ago First seen · 142 lines · 173 tokens per session scan C 72dcff9e9541
tomtom-mcp-docs-update-pr is a skill published in the GitHub repository tomtom-international/tomtom-maps-mcp (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 173 tokens to every session and 2,390 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-19.
Other skills, from other repositories
site-config-creation
Create or update the [site] section of stencila.toml for published Stencila sites. Use when asked to configure site domain, title, author, logo, icons, labels, descriptions, socials, featured content, navigation, routes, access, layout presets and regions, glide, search, formats, reviews, uploads, remotes, actions…
code-review
Coordinate a delegated full multi-persona code review for a Moraine PR or local change. Use when asked to review a PR, run review agents, get code review feedback, or iterate on review feedback using all CodeReview personas: elegance, idiom, correctness, completeness, security, YAGNI, and scope. Invoking this skill is…
faceted-navigation
Let shoppers filter products by multiple attributes simultaneously with URL-shareable filter state, instant results, and mobile-friendly controls.
code-review-elegance
Review a PR through the CodeReviewElegance persona. Use when asked to review code for minimal design, architectural leverage, elegant abstractions, simplification, removing unnecessary moving parts, or finding the design move that sidesteps an entire class of problems.
code-review-idomatic
Review a PR through the CodeReviewIdomatic persona. Use when asked to check whether code is idiomatic for the implementation language, follows standard library and ecosystem conventions, avoids unnecessarily novel implementations, and matches established patterns in this repository.
code-review-security-review
Review a PR through the CodeReviewSecurityReview persona. Use when asked to check whether code is safe, avoids backdoors, vulnerable dependencies, injection attacks, auth bypasses, secret leaks, unsafe file/network behavior, and other security regressions.