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.
git clone --depth 1 https://github.com/MilindGaharwar/fettleWrote 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/milindgaharwar/fettle/baseline)<a href="https://agentmods.dev/commands/milindgaharwar/fettle/baseline"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/baseline/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/commands/milindgaharwar/fettle/baseline"><img src="https://agentmods.dev/badge/commands/milindgaharwar/fettle/baseline.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.00000 | $0.00123 |
| Opus 5.5 | $0.00000 | $0.00049 |
| Sonnet 5.5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
baseline 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 1mo 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.
This is a copy
88% identical to fettle-baseline — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/fettle:baseline
Manage violation baselines for gradual adoption.
Usage
Create baseline (snapshot current state)
fettle baseline create
Saves all current findings to .fettle-baseline.json. These findings are grandfathered.
Check against baseline (only new violations)
fettle check --baseline
Update baseline (after fixing some findings)
fettle baseline update
Purpose
Allows adoption in legacy repos without fixing all existing issues first. Only NEW violations are reported; existing ones are tracked but not blocking.
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.
- 1mo ago First seen · 27 lines · 0 tokens per session scan A d59f085c31e8
baseline is a command published in the GitHub repository MilindGaharwar/fettle (4 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 123 tokens. A static security scan graded it A with 0 findings. It is 88% identical to fettle-baseline, differing in 6 lines, and is treated as a copy.
Other commands, from other repositories
apex-quick
Quick Flow for bounded fixes - the full APEX route with Brainstorm skipped and Plan compressed to one task; Analyze trio, delegated execution, eLicit, Verify, challenger and full sniper always run.
explain-error
Explains an error found in a log file and proposes a next step.
debug-files
Command "debug-files" from getsentry/toolkit, covering notes on find and important notes.
fix-issues
Pick up one approved task, implement the fix, and close it.
release
A typical CI release creates the release, associates commits, finalizes it, and records a deploy.
security-audit
Full security review — GitHub alerts, static code analysis, live app check — then a task per finding.