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/mitsuhiko/agent-stuff/anachbnpx skills add mitsuhiko/agent-stuff --skill anachbgit clone --depth 1 https://github.com/mitsuhiko/agent-stuffWrote 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/mitsuhiko/agent-stuff/anachb)<a href="https://agentmods.dev/skills/mitsuhiko/agent-stuff/anachb"><img src="https://agentmods.dev/badge/skills/mitsuhiko/agent-stuff/anachb.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.00065 | $0.01344 |
| Opus 5 | $0.00032 | $0.00672 |
| Sonnet 5 | $0.00013 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
anachb scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "https://vao.demo.hafas.de/gate" \ How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VOR AnachB - Austrian Public Transport API
Query Austrian public transport for real-time departures, route planning, and service disruptions using the HAFAS API.
Quick Reference
| Script | Purpose |
|---|---|
search.sh |
Find stations/stops by name |
departures.sh |
Real-time departures at a station |
route.sh |
Plan a trip between two locations |
disruptions.sh |
Current service disruptions |
API: HAFAS (Hacon Fahrplan-Auskunfts-System)
Endpoint: https://vao.demo.hafas.de/gate
1. Search Stations/Stops
Find station IDs by name:
./search.sh "Stephansplatz"
./search.sh "Wien Hauptbahnhof"
./search.sh "Linz"
./search.sh "Salzburg Hbf"
Returns station names, IDs (extId), and coordinates.
Response fields:
name: Station nameextId: Station ID for use in other queriestype: S (Station), A (Address), P (POI)coordinates: WGS84 coordinates (lon/lat in 1e-6 format)
2. Real-Time Departures
Get next departures from a station:
./departures.sh <station-id> [count]
# Examples:
./departures.sh 490132000 # Wien Stephansplatz, 10 departures
./departures.sh 490132000 20 # Wien Stephansplatz, 20 departures
./departures.sh 490060200 # Wien Hauptbahnhof
./departures.sh 444130000 # Linz Hbf
./departures.sh 455000100 # Salzburg Hbf
Response fields:
line: Line name (U1, S1, RJ, etc.)direction: Final destinationdeparture: Scheduled departure timedelay: Delay in minutes (if any)platform: Platform/track number
3. Route Planning
Plan a trip between two stations:
./route.sh <from-id> <to-id> [results]
# Examples:
./route.sh 490132000 490060200 # Stephansplatz → Hauptbahnhof
./route.sh 490132000 444130000 5 # Wien → Linz, 5 results
./route.sh "Graz Hbf" "Wien Hbf" # Search by name (slower)
Response fields:
departure: Departure timearrival: Arrival timeduration: Trip durationchanges: Number of transferslegs: Array of trip segments with line info
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 184 lines · 65 tokens per session scan A 80f9a9c3d360
anachb is a skill published in the GitHub repository mitsuhiko/agent-stuff (3,044 stars, last pushed 2d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,344 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…