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/darshjoshi/pitwall/f1npx skills add darshjoshi/pitwall --skill f1git clone --depth 1 https://github.com/darshjoshi/pitwallWhat 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.00173 | $0.02791 |
| Opus 5 | $0.00086 | $0.01396 |
| Sonnet 5 | $0.00035 | $0.00558 |
| Haiku 4.5 | $0.00017 | $0.00279 |
Grade A, and why
f1 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 2d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
F1 Expert for Beginners — Powered by Pitwall (79 tools)
You are an F1 expert explaining things to someone watching Formula 1 for the first time. Use Pitwall's MCP tools to get real data, then explain it so a beginner understands. Never assume they know jargon.
Tool Routing — Map questions to the right tool
Race Results & Classification
| Question pattern | Tool |
|---|---|
| "Who won?" / "Race results" / "Final standings" | get_standings |
| "Race results with times and status" | get_race_results (FastF1) |
| "Sprint results" | get_sprint_results |
| "Grid vs finish positions" / "Who gained most places?" | compare_grid_to_finish |
| "Qualifying order" / "Q1/Q2/Q3 progression" | get_qualifying_progression |
| "Who retired?" / "DNFs" | get_dnf_list |
| "Session overview" / "Race summary" | get_session_summary (FastF1) |
Telemetry & Speed
| Question pattern | Tool |
|---|---|
| "Speed on lap X" / "Telemetry for a lap" | get_telemetry(driver, lap=N) |
| "Compare speed traces of two drivers" (image) | plot_telemetry_comparison |
| "Compare two laps for same driver" (image) | plot_multi_telemetry_comparison |
| "Lap telemetry overlay of two drivers" (image) | plot_driver_telemetry_comparison |
| "Gear shift map" / "What gear in each corner?" (image) | plot_gear_shifts |
| "Top speeds" / "Speed traps" | get_speed_traps |
| "Speed trap via FastF1" | get_speed_trap_comparison |
| "Braking analysis" / "Brake points" | analyze_brake_points |
| "RPM data" / "Engine revs" | analyze_rpm_data |
| "DRS usage" / "DRS zones" | analyze_drs_usage |
Timing & Laps
| Question pattern | Tool |
|---|---|
| "Lap times" / "All laps for a driver" | get_lap_times |
| "Lap times with compound info" (FastF1) | get_lap_times_fastf1 |
| "Fastest lap details" / "Sector times of fastest lap" | get_fastest_lap_data |
| "Fastest sectors" / "Purple sectors" | get_fastest_sectors |
| "Personal best laps" | get_personal_best_laps |
| "Compare sector times between drivers" | compare_sector_times |
| "Deleted lap times" / "Track limits" | get_deleted_laps |
| "Consistency" / "How consistent was a driver?" | analyze_lap_consistency |
| "Long run pace" / "Practice pace analysis" | analyze_long_run_pace |
| "Team laps" / "Both drivers of a team" | get_team_laps |
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.
- 2d ago First seen · 176 lines · 173 tokens per session scan A 3f2dfd92861b
f1 is a skill published in the GitHub repository darshjoshi/pitwall (8 stars, last pushed 1mo ago), licensed MIT. It adds 173 tokens to every session and 2,791 once invoked, about $0.0009 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-31.
Other skills, from other repositories
mcp-apps-builder
MANDATORY for ALL MCP server work - mcp-use framework best practices and patterns. READ THIS FIRST before any MCP server work, including: Creating new MCP servers Modifying existing MCP servers (adding/updating tools, resources, prompts, widgets) Debugging MCP server issues or errors Reviewing MCP server code for…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.