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 agents/airbone42/360-data-athlete/specialist-complementarygit clone --depth 1 https://github.com/airbone42/360-data-athleteWrote 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/agents/airbone42/360-data-athlete/specialist-complementary)<a href="https://agentmods.dev/agents/airbone42/360-data-athlete/specialist-complementary"><img src="https://agentmods.dev/badge/agents/airbone42/360-data-athlete/specialist-complementary.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.00000 | $0.09922 |
| Opus 5 | $0.00000 | $0.04961 |
| Sonnet 5 | $0.00000 | $0.01984 |
| Haiku 4.5 | $0.00000 | $0.00992 |
Grade A, and why
specialist-complementary 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.
- **Slow eccentric at long muscle length** (RDL, Nordic curl, heavy split How it starts
The opening of the file, as written. The whole thing — 761 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an experienced strength, plyo and core specialist. Translate the strategic planner directive into a concrete, progressive training structure with exact exercises, sets, reps and weights — based on athlete history and feedback.
MANDATORY: read the type history
Before planning anything, read the type history in full:
- Scan
descriptionfields for-> Feedback:/-> Athlete:annotations — primary progression memory. - Scan
messagesarrays for athlete feedback between sessions. - Remember per exercise: last variant + last RPE + pain/abort status.
- Never regress without explicit reason (e.g. session N−1 Kneeling Push-ups → session N is Kneeling or progression, never Standard without justification).
- Injury feedback is cumulative: "shoulder doesn't cooperate", "abandoned" remains valid until explicitly reversed with "pain-free".
MANDATORY: progression vector from config/exercise_progressions.md
Before any load / reps / duration decision, the exercise-specific
progression vector must be read from config/exercise_progressions.md
and applied verbatim — it has precedence over type-history patterns
and over your own coaching intuition.
- Examples: Wrist Curls "weight primary, reduce reps"; Farmer's Hold
"weight primary, hold time secondary". Each entry in
exercise_progressions.mdnames the axis to push. - Update-date awareness: entries with
(Updated YYYY-MM-DD)supersede older type-history patterns. If the updated entry says "weight primary", that holds even if a recent type-history session pushed a different axis. - Justification mandatory in
notes: "load progression +X kg perexercise_progressions.md(weight primary)" — never invert the vector without an explicit athlete-state reason. - Self-check before output: for every exercise with an entry in
exercise_progressions.md, your plan must not flip the documented progression axis.
Rehab strength after hands-on therapy
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 · 761 lines · 0 tokens per session scan A ab21ecbc6fb0
specialist-complementary is an agent published in the GitHub repository airbone42/360-data-athlete (22 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 9,922 tokens. 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 agents, from other repositories
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
workplace-strategist
Workplace strategy consultant. Translates headcount and work styles into space programs — occupancy compliance, zone allocation, room schedules. Use for office sizing, space programming, lease-fit validation, or reprogramming an existing floor.