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/odere-pro/claude-calibration/calibration-diffnpx skills add odere-pro/claude-calibration --skill calibration-diffgit clone --depth 1 https://github.com/odere-pro/claude-calibrationWrote 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/odere-pro/claude-calibration/calibration-diff)<a href="https://agentmods.dev/skills/odere-pro/claude-calibration/calibration-diff"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibration-diff.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.1 | $0.00110 | $0.01171 |
| Opus 5 | $0.00055 | $0.00585 |
| Sonnet 5 | $0.00022 | $0.00234 |
| Haiku 4.5 | $0.00011 | $0.00117 |
Grade B, and why
calibration-diff scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
CURRENT="$(cat .claude/calibration/current)" How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
echo "=== calibration-diff preprocessing ==="
DOCS_DIR="$(cd "${CLAUDE_SKILL_DIR}/../../docs" 2>/dev/null && pwd || echo UNKNOWN)"
BUNDLES_DIR="$(cd "${CLAUDE_SKILL_DIR}/.." 2>/dev/null && pwd || echo UNKNOWN)"
echo "DOCS_DIR=$DOCS_DIR"
echo "BUNDLES_DIR=$BUNDLES_DIR"
echo "PROJECT_DIR=${CLAUDE_PROJECT_DIR:-$(pwd)}"
echo "NOW_ISO=$(date -u +%Y-%m-%dT%H:%M:%SZ)"
echo "GIT_HEAD=$(git rev-parse HEAD 2>/dev/null || echo not-a-git-repo)"
if [ -f .claude/calibration/current ]; then
CURRENT="$(cat .claude/calibration/current)"
echo "CURRENT_RUN=$CURRENT"
else
echo "CURRENT_RUN=(none)"
fi
echo "--- recent calibration runs (newest first) ---"
ls -1dt .claude/calibration/*/ 2>/dev/null | head -5 || echo "(none)"
echo "=== end preprocessing ==="
calibration-diff — re-evaluate against the last baseline
You are the diff-only flow. You run the calibration evaluator pass 2 against the previous run's baseline reports and stop. No planner, no calibrator, no edits.
What to do
- Resolve
DOCS_DIR,BUNDLES_DIR,PROJECT_DIRfrom the preprocessing block. - Pick the run to diff against. Default: the latest run folder with a complete
baseline_reportslist inplan.md(read it; the field is set when the evaluator finishes Pass 1). If the user passed a run identifier in$ARGUMENTS(e.g. a timestamp), use that one. If no run is found, print one line:No prior calibration run found — run /calibrate first to establish a baseline.and stop. Also read the picked run'splugin_filterfield — the delta must re-audit the same plugin scope as the baseline, so reuse it verbatim (don't take a new--pluginsflag here). - Spawn the evaluator (Pass 2):
The evaluator will writeAgent(calibration-evaluator) Pass: 2 (delta). Run folder: <abs of the picked run>. Plan: <run>/plan.md. Baseline reports: <the names from plan.md baseline_reports>. Rubric dir: <DOCS_DIR>. Bundles dir: <BUNDLES_DIR>. Project dir: <PROJECT_DIR>. Plugin filter: <the picked run's plugin_filter from plan.md, or empty = all plugins>.eval-delta-<ts>.mdinto the run folder and updateplan.md'slast_evaluationfield. - Print a short summary. Read
plan.md's now-updatedlast_evaluationfield; print:Diffing against: <run folder> (baseline taken <plan.started>).Before: C<n> H<n> M<n> L<n>. After: C<n> H<n> M<n> L<n>.Resolved <n> · partial <n> · open <n> · new <n>.Delta report: <run>/eval-delta-<ts>.md.→ Run /calibrate to plan fixes for the open + new findings.
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 · 85 lines · 110 tokens per session scan B 555964af187e
calibration-diff is a skill published in the GitHub repository odere-pro/claude-calibration (1 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,171 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
verifying-external-behavior
Confirms what a third-party library, remote API, build backend, or scraped document actually does before writing code that depends on it — throwaway probes that run in seconds, permissive clients that forward wrong arguments instead of rejecting them, per-endpoint docs that don't generalize, response shapes that make…
codebase-navigator
Deep structural codebase comprehension, AST dependency graph traversal, symbol caller/callee tracing, and monorepo navigation strategies for massive codebases.
root-cause-analysis
Hyper-scale root cause analysis (RCA), bisection, call-tree backtracking, and automated surgical remediation across massive million-file enterprise repositories.
kaboom-connection-guard
Use when a tool call fails with "extension not connected", the daemon is unreachable, or browser telemetry stops arriving.
devflow
Full-lifecycle AI development workflow — auto-detects whether you need design, build, or fix mode, then enforces the right pipeline with hard gates at every stage. Fuses grill-with-docs, OpenSpec, and superpowers methodology.
config-doctor
Use when MCP tools fail to connect, user reports "extension not connected", tool calls return errors, or user asks to check their Kaboom setup.