Borrowing it
Nothing to install: this file belongs to snoozelieb/coach-mcp. 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/snoozelieb/coach-mcp/main/.claude/skills/capture-fixtures/SKILL.mdgit clone --depth 1 https://github.com/snoozelieb/coach-mcpWrote 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/snoozelieb/coach-mcp/capture-fixtures)<a href="https://agentmods.dev/skills/snoozelieb/coach-mcp/capture-fixtures"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/capture-fixtures/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/skills/snoozelieb/coach-mcp/capture-fixtures"><img src="https://agentmods.dev/badge/skills/snoozelieb/coach-mcp/capture-fixtures.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.00055 | $0.00501 |
| Opus 5 | $0.00028 | $0.00251 |
| Sonnet 5 | $0.00011 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
capture-fixtures 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 12d 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
Refreshing Garmin test fixtures
The rule that matters most
python scripts/capture_fixtures.py hits the live Garmin API with the owner's
session and writes personal health data. Agents and CI must NEVER run it.
Ask the user to run it themselves — suggest the ! prefix so the output lands
in the session:
! python scripts/capture_fixtures.py
How the two-layer fixture system works
tests/fixtures/garmin_sample.json— committed, fully synthetic values with real response shapes. Clean checkouts run every fixture-driven test from this alone.test_fixtures.json(repo root) — the real capture, gitignored (even redacted it contains sleep/HRV/weight/load data). Thegarmin_fixturesfixture intests/conftest.pyloads the sample first and overlays the real capture where present, so real-shape regressions surface on the owner's machine while clean checkouts stay green.
The capture script redacts obvious PII before writing (names/emails → "REDACTED", profile/device ids → 0, GPS coordinates removed).
When to refresh
- A garminconnect upgrade or Garmin API change alters response shapes
(
tests/test_garmin_contract.pyfailing is the usual tell). - A new endpoint was added to the codebase — also add it to the capture list
in
scripts/capture_fixtures.pyand a synthetic shape togarmin_sample.json+ FakeGarminClient.
Prerequisites & verification
- Valid Garmin session (
.garth/tokens or credentials in.env); if auth fails:python scripts/garmin_login.py(also owner-run — interactive MFA). - Afterwards: confirm
git statusdoes NOT listtest_fixtures.json(it must stay gitignored), thenpython -m pytest -q— real shapes now overlay the synthetic ones.
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.
- 12d ago First seen · 48 lines · 55 tokens per session scan A a40725a0f078
capture-fixtures is a skill published in the GitHub repository snoozelieb/coach-mcp (2 stars, last pushed 15d ago), licensed MIT. It adds 55 tokens to every session and 501 once invoked, about $0.0003 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.