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-preflight/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-preflight)<a href="https://agentmods.dev/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-preflight"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-preflight/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-preflight"><img src="https://agentmods.dev/badge/skills/tomtom-international/tomtom-maps-mcp/tomtom-mcp-preflight.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.00250 | $0.04580 |
| Opus 5.5 | $0.00100 | $0.01832 |
| Sonnet 5.5 | $0.00050 | $0.00916 |
| Haiku 4.5 | $0.00025 | $0.00458 |
Grade A, and why
tomtom-mcp-preflight 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 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.
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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate the working diff before it becomes a commit or PR. Consistency and completeness, not bug
hunting. CODING_GUIDELINES.md holds the rules; Step 4 verifies the
diff against them. There are no git hooks in this repository, so every gate below is a CI job or
nothing — which is why .claude/settings.json and .cursor/hooks.json deny git commit until this
skill has passed once in the session (Step 8).
The commands are POSIX shell: Git Bash on Windows, which Claude Code's Bash tool uses. Searches use
rg — on Windows winget install BurntSushi.ripgrep.MSVC, or use the agent's own search tool.
- Fix: Biome autofixes on touched files, generated churn, stale references after a rename, doc rows derivable from the code, debug artifacts, Step 4.
- Report: anything needing invented intent — new prose, an ADR, naming judgement, whether an untracked file belongs in the commit, whether a change is breaking.
Step 1: Scope
git status --short,git diff,git diff --cached→ the touched files and the areas driving Step 2. Scope everything below to those; never audit the whole repo unless asked to — then run every gate and search over the whole tree, and fix only what needs no invented intent.- Read untracked files fully — no baseline, and the likeliest source of Step 5 problems.
- Generated churn:
pnpm buildrewritessrc/version.tsand theversionofmanifest-binary.jsonfrompackage.json. A diff in either that the change did not intend is churn —git checkout --it. Versions are bumped byprepare-release.ymlon release, never by hand. - Stage explicit paths afterwards, not
git add -A.
Step 2: Gates
Two tiers, each scoped to what the diff touches:
- Commit — what the commit gate asks for. No build, no API key, no quota; under half a minute.
- Push — before pushing or opening a PR, add the push rows. They are the gates of
Adding_new_tools.md§ Before opening a PR and what PR CI runs;quality_checks.ymlandbuild-mcpb.ymlown the order.
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 Changed · +27 lines · +39 tokens per session fd0513a91219
- 14d ago Changed · +12 tokens per session bf4cc365eb3f
- 16d ago First seen · 226 lines · 199 tokens per session scan A c34ffc6cb00b
tomtom-mcp-preflight is a skill published in the GitHub repository tomtom-international/tomtom-maps-mcp (59 stars, last pushed yesterday), licensed Apache-2.0. It adds 250 tokens to every session and 4,580 once invoked, about $0.0010 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
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.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.