Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Darwin-Agent/Car-bench-TRACE --skill navigation-remove-waypointgit clone --depth 1 https://github.com/Darwin-Agent/Car-bench-TRACEWrote 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/darwin-agent/car-bench-trace/navigation-remove-waypoint)<a href="https://agentmods.dev/skills/darwin-agent/car-bench-trace/navigation-remove-waypoint"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/navigation-remove-waypoint/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/darwin-agent/car-bench-trace/navigation-remove-waypoint"><img src="https://agentmods.dev/badge/skills/darwin-agent/car-bench-trace/navigation-remove-waypoint.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.00000 | $0.03749 |
| Opus 5 | $0.00000 | $0.01875 |
| Sonnet 5 | $0.00000 | $0.00750 |
| Haiku 4.5 | $0.00000 | $0.00375 |
Grade C, and why
navigation-remove-waypoint 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- **The needed delete tool is absent (the common case).** Detect this *before* fetching the replacement leg or asking the user to choose a route — pulling alternatives and asking "fastest or shortest?" for a removal you How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove a stop or destination from a route
A route is active and the user wants to drop one of its waypoints. The same method handles the clear case, the under-specified one (which stop?), and the missing-capability one (no delete tool callable). The first decision after reading the state is which kind of waypoint the target is, because the two cases use different tools and have different preconditions:
- The final destination (the user wants the trip to end earlier — "make X my last stop", "I don't want to continue to Y", "cancel the destination") →
navigation_delete_destination. No replacement route is needed: the last intermediate stop simply becomes the new destination. - An intermediate stop (the user wants to skip the middle and go direct over that leg) →
navigation_delete_waypoint, which requires a replacement route for the leg that becomes direct.
You always read the current navigation state first to resolve which waypoint is meant and where it sits. The recurring twist in this operation: the specific delete tool you need is often the missing one — frequently there is no way to remove that waypoint while keeping the route active, and the honest answer is then a clear "no" plus a forward offer.
When this applies
"Drop the middle stop and go straight there", "skip the intermediate stop", "I don't need to stop at anymore", "remove from my route", "cancel ", "make my final destination / last stop", "I don't want to continue to " — while navigation is active. It covers removing an intermediate stop and removing the final endpoint, because both are "take a waypoint out of my active route". (To swap a stop or destination for a different place, that is navigation-change-destination / a replace skill, not this one — removal shortens the route, replacement keeps the same number of stops.)
Tools
get_current_navigation_state({detailed_information:true})— read the ordered waypoint list (index 0 is the start, last index is the destination, anything between is intermediate), the start, and the current routes. This is how you map the user's words to the right id. May be missing, or may return"unknown"for the waypoint/route fields (then the ids are unreadable and you cannot safely edit).get_routes_from_start_to_destination({start_id, destination_id})— fetch route alternatives for the leg that becomes direct once an intermediate stop is gone: start → the stop after the removed one. Not needed when removing the final destination.get_location_id_by_location_name({location})— resolve a named place to an id when needed (use the city main name only).navigation_delete_waypoint({route_id_without_waypoint, waypoint_id_to_delete})— delete an intermediate stop, supplying the chosen route for the now-direct leg. Only works while navigation is active and a multi-stop route is set.navigation_delete_destination({destination_id_to_delete})— delete the final destination; the previous waypoint becomes the new destination. Only works while active and a multi-stop route is set — a route must always keep at least a start and a destination, so this is blocked when there is no intermediate stop left to promote.
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 · 92 lines · 0 tokens per session scan C 386cd428ebd0
navigation-remove-waypoint is a skill published in the GitHub repository Darwin-Agent/Car-bench-TRACE (8 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,749 tokens. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…