Borrowing it
Nothing to install: this file belongs to elias-ramzi/ClaudeCyclingMCP. 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/elias-ramzi/ClaudeCyclingMCP/main/CLAUDE.mdgit clone --depth 1 https://github.com/elias-ramzi/ClaudeCyclingMCPWrote 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/instructions/elias-ramzi/claudecyclingmcp/claude-md)<a href="https://agentmods.dev/instructions/elias-ramzi/claudecyclingmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/elias-ramzi/claudecyclingmcp/claude-md/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/instructions/elias-ramzi/claudecyclingmcp/claude-md"><img src="https://agentmods.dev/badge/instructions/elias-ramzi/claudecyclingmcp/claude-md.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.01150 | $0.01150 |
| Opus 5 | $0.00575 | $0.00575 |
| Sonnet 5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
ClaudeCyclingMCP CLAUDE.md 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guide
Architecture and conventions for anyone — human or agent — working in this repo.
The shape of it
One canonical spec in, two renderers out:
spec (JSON) → validate → resolved Workout tree ──┬── render_zwo → .zwo (MyWhoosh)
(power as fractions of FTP)└── render_garmin → JSON (Garmin)
| Module | Holds |
|---|---|
spec.py |
parse, validate, normalise. Produces a Workout of Block/Repeat nodes with all power as fractions of FTP — the single representation both renderers consume. |
metrics.py |
1 Hz power series, NP/IF/TSS, and the describe_spec table. |
render_zwo.py |
MyWhoosh XML. Hand-built strings, not ElementTree, to control the exact format. |
render_garmin.py |
Garmin upload_workout payload. |
verify.py |
compare what a platform stored against what was sent: Garmin's returned payload, and MyWhoosh's scraped builder header. |
skills.py |
load .claude/skills/*/SKILL.md and serve them as MCP prompts. |
server.py |
the MCP tool surface. Thin — logic lives in the modules above. |
Fractions of FTP are the internal currency. Watts are converted in at parse time and out at render time. If you find yourself carrying watts through the middle of the pipeline, that's a smell.
Rules that are load-bearing
These encode things that were expensive to learn. Changing them needs evidence, not reasoning.
Garmin: power targets are workoutTargetTypeId 2 (power.zone) with targetValueOne/Two in
watts. Not id 6 / power.between, despite what the Garmin MCP's tool description says — id 6
uploads cleanly and Garmin stores it as a pace target on a cycling workout. A %FTP target is the
same id-2 shape plus targetValueUnit: {"unitId": 253, "unitKey": "percent"}; watts carry no unit
object at all.
Garmin: never trust the curated read. get_workout_by_id drops targetValueUnit, so watts and
percentages are indistinguishable through it, and its estimated_duration_seconds disagrees with
the sum of the steps. Verify against what was sent.
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 · 88 lines · 1,150 tokens per session scan A bc10509af8e8
ClaudeCyclingMCP CLAUDE.md is an instructions file published in the GitHub repository elias-ramzi/ClaudeCyclingMCP (0 stars, last pushed 16d ago), licensed MIT. It adds 1,150 tokens to every session, about $0.0057 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).