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 agentmods add skills/rlacombe/switchback-running/racenpx skills add rlacombe/switchback-running --skill racegit clone --depth 1 https://github.com/rlacombe/switchback-runningWrote 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/rlacombe/switchback-running/race)<a href="https://agentmods.dev/skills/rlacombe/switchback-running/race"><img src="https://agentmods.dev/badge/skills/rlacombe/switchback-running/race.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00882 |
| Opus 5 | $0.00009 | $0.00441 |
| Sonnet 5 | $0.00004 | $0.00176 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
race 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 3d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/race — Race-Day Strategy
Builds a comprehensive race-day plan for the athlete's target race. The user may specify a race or default to the one in their athlete profile.
Step 1: Read knowledge base
Read these coaching files for expert protocols:
knowledge/race-execution.md— pacing, ADAPT framework, aid stationsknowledge/taper.md— taper check, sharpeningknowledge/nutrition.md— cal/hr, carb/hr, fluid targets, Bullseye planknowledge/heat-altitude.md— environmental preparationknowledge/mental-performance.md— associative/dissociative strategies, crisis protocols
Step 2: Gather data
Fetch data using MCP tools (call them directly, in parallel where possible):
- Fitness endpoint for the last 21 days — CTL/ATL/TSB trend into race day
- Events endpoint for the next 14 days — remaining workouts and taper check
- Activities endpoint for the last 30 days — recent training volume and long runs
- Wellness endpoint for the last 7 days — sleep, HRV, fatigue trends
Read athlete/profile.md for race details (distance, elevation, cutoffs, key cutoffs) and cached zones.
Step 3: Build the race plan
Pacing Strategy
- Estimate finish time range based on current CTL, recent long run performances, and race profile
- Break the race into segments (e.g., by aid station) with target pace ranges
- Flag any tight cutoffs given projected pace
- Account for elevation — slower on climbs, faster on descents, with specific pace adjustments
- Reference Koop's "stay in the moment" pacing — focus on current segment, not the whole race
Nutrition Plan
- Set cal/hr and carb/hr targets based on athlete weight and expected intensity (use
knowledge/nutrition.md) - Plan what to carry vs pick up at aid stations
- Fluid and sodium targets (600-800mg sodium/L)
- Gut training check — has the athlete practiced this plan in training?
- Warn about under-fueling (most ultrarunners consume 80-120 cal/hr vs 240-260 recommended)
Aid Station Plan
- Time estimate for each aid station based on pacing
- What to do at each stop: refill, eat, gear change, crew access
- Keep it efficient — get in, get out (Koop)
- Mark crew-accessible stations and drop bag locations
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.
- 3d ago First seen · 82 lines · 18 tokens per session scan A 5ba59793bb24
race is a skill published in the GitHub repository rlacombe/switchback-running (11 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 882 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
platform-api
Queries the Genesys Cloud Platform API schema for endpoint details, permissions, parameters, and response formats. Use when user asks about Genesys Cloud API endpoints (e.g., "/api/v2/assistants/queues"), API documentation, API permissions, schemas, capabilities, or when implementing Genesys Cloud operations.
google-adk-python
Build production-ready AI agents in Python using Google Agent Development Kit (ADK). Use when creating agentic Python applications with LlmAgent, workflow agents (SequentialAgent, ParallelAgent, LoopAgent), multi-agent orchestration, tool development (function tools, MCP, OpenAPI), session and state management…
google-adk-typescript
Build production-ready AI agents in TypeScript using Google Agent Development Kit (ADK). Use when creating agentic TypeScript/JavaScript applications with LlmAgent, workflow agents (SequentialAgent, ParallelAgent, LoopAgent), custom agents (BaseAgent with runAsyncImpl), FunctionTool with Zod schemas, MCP and OpenAPI…
qmd
Search the vault using QMD semantic search. Use PROACTIVELY before reading files. Preference order: (1) MCP tools — mcpqmdquery, mcpqmdget, mcpqmdmultiget, mcpqmdstatus — if they appear in your tool menu, use them first; (2) CLI qmd --index ... as fallback; (3) Grep/Glob only when QMD is not installed. Trigger…
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…
wiki-query
Fast, read-only, index-first llm-wiki queries for OpenCode and compatible instruction-file harnesses.