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/rbrands/intervals-icu-sync/skillnpx skills add rbrands/intervals-icu-sync --skill skillgit clone --depth 1 https://github.com/rbrands/intervals-icu-syncWrote 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/rbrands/intervals-icu-sync/skill)<a href="https://agentmods.dev/skills/rbrands/intervals-icu-sync/skill"><img src="https://agentmods.dev/badge/skills/rbrands/intervals-icu-sync/skill.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.00090 | $0.00244 |
| Opus 5 | $0.00045 | $0.00122 |
| Sonnet 5 | $0.00018 | $0.00049 |
| Haiku 4.5 | $0.00009 | $0.00024 |
Grade A, and why
training-plan-generation 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 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.
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.
What it actually says
Training Plan Generation
This skill guides plan generation and workout selection for the training architect agent.
Scope
Use this skill when the user requests one of the following:
- create a weekly plan
- suggest workouts based on limiter and goals
- adapt sessions for fatigue, recovery, or race proximity
References
- references/decision-process.md — follow this decision sequence
- references/workout-library.md — read when selecting concrete workouts/tags
Rules
- Follow the decision sequence from decision-process.md.
- Select workouts and tags from workout-library.md.
- Keep output deterministic and aligned with the agent output contract.
- If required inputs are missing, ask only the minimum required question.
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 · 31 lines · 90 tokens per session scan A 1c62bceb4257
training-plan-generation is a skill published in the GitHub repository rbrands/intervals-icu-sync (16 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 244 once invoked, about $0.0005 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
montis-coaching
Interpret authorized Montis.icu and Intervals.icu endurance data, generate governed coaching decisions, analyze activities, plan training, and safely manage calendar workflows.
add-tool
Step-by-step guide for adding a new MCP tool to this Intervals.icu server. Use when the user wants to add a new tool, endpoint, or API integration. Ensures the established async pattern, response format, naming discipline, and LLM-facing token budgets are followed consistently.
release-write
Write release notes for a new version and cut the release. Use when the user wants to ship a tagged release after merging the release CHANGELOG commit. Produces a clean GitHub Release body sourced from CHANGELOG.md, then tags + publishes.
commit
Analyze changes, write a conventional commit, and (when shipping) open a PR with closing keywords so referenced issues auto-close on merge. Use when the user asks to commit, push, or open a PR.
release-check
Run the full pre-release verification suite and summarize results. Use when the user asks to check if the code is ready for release, before any PR/merge, or when finishing a feature.
section-11
Evidence-based endurance coaching protocol (v11.63). Use when analyzing training data, reviewing sessions, generating pre/post-workout reports, planning workouts, answering training questions, or giving endurance coaching advice. Always read or fetch athlete JSON data before responding to any training question.