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 commands/satanyakiv/nutrisport/fixgit clone --depth 1 https://github.com/satanyakiv/NutriSportWrote 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/commands/satanyakiv/nutrisport/fix)<a href="https://agentmods.dev/commands/satanyakiv/nutrisport/fix"><img src="https://agentmods.dev/badge/commands/satanyakiv/nutrisport/fix.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.00393 |
| Opus 5 | $0.00000 | $0.00197 |
| Sonnet 5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
fix 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 5d 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
Read .claude/rules/architecture.md, .claude/rules/error-handling.md, .claude/rules/testing.md
Bug
$ARGUMENTS
Process (TDD — Red-Green-Refactor)
-
REPRODUCE: Find the relevant code. Trace the data flow:
Screen → ViewModel → UseCase → Repository → DataSourceShow: what's wrong, why, which layer, file paths + line numbers. Wait for "go". -
RED — Write a failing test first:
- Name:
`should {expected} when {condition}` - AAA pattern, Mokkery for mocks, Turbine for Flows
- Run:
./gradlew :{module}:allTests --tests "*TestClass"— confirm FAILS
- Name:
-
GREEN — Minimal fix:
- Fix only the bug, nothing else
- Respect layer boundaries: DTOs in data, domain stays pure, Ui in feature
- If fix crosses layers — fix in the correct layer per architecture
-
VERIFY:
- New test PASSES
- All tests in affected module(s) PASS:
./gradlew :{module}:allTests - Compile check:
./gradlew :{module}:compileCommonMainKotlinMetadata
-
UPDATE rules if the bug revealed an undocumented gotcha:
- Add to
.claude/rules/conventions.mdor CLAUDE.md Build Gotchas
- Add to
Rules
- Never
./gradlew testwithout--testsfilter - Never break existing tests
- Minimal diff — don't touch what isn't broken
- If fix needs a new UseCase → follow architecture rules
- If fix needs model changes → update mappers in ALL layers
- If unsure → ask, don't guess
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.
- 5d ago First seen · 40 lines · 0 tokens per session scan A 02dc32e47552
fix is a command published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 393 tokens. 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 commands, from other repositories
tdd-requirements
TDD開発の要件整理を行います。機能要件を明確化し、テスト駆動開発のための準備を行います。.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化(設計レビュー→作業計画→TDD実装).
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.