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 skills add odere-pro/claude-calibration --skill calibration-auditgit 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-audit)<a href="https://agentmods.dev/skills/odere-pro/claude-calibration/calibration-audit"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibration-audit/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/odere-pro/claude-calibration/calibration-audit"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibration-audit.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.00151 | $0.01508 |
| Opus 5 | $0.00076 | $0.00754 |
| Sonnet 5 | $0.00030 | $0.00302 |
| Haiku 4.5 | $0.00015 | $0.00151 |
Grade A, and why
calibration-audit 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 10d 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 directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Otherwise resume the latest audit folder (find via `ls -1dt .claude/calibration/*/ | head -1`). Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
echo "=== calibration-audit 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 "TIMESTAMP=$(date +%Y%m%d-%H%M%S)"
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)"
echo "GITIGNORE_HAS_CALIBRATION=$(grep -qs 'calibration' .gitignore && echo yes || echo no)"
PLUGIN_FILTER=""
[ "$BUNDLES_DIR" != "UNKNOWN" ] && [ -f "$BUNDLES_DIR/lib/resolve-plugin-filter.sh" ] && PLUGIN_FILTER="$(bash "$BUNDLES_DIR/lib/resolve-plugin-filter.sh" "$ARGUMENTS" "${CLAUDE_PROJECT_DIR:-$(pwd)}" 2>/dev/null || true)"
echo "PLUGIN_FILTER=$PLUGIN_FILTER"
echo "=== end preprocessing ==="
calibration-audit — read-only baseline
You are the audit-only flow. Your job is to chain calibration-planner (init) and
calibration-evaluator (pass 1) — exactly the first two phases of /calibrate — and then stop.
No improvement plan; no approval gate; no calibrator. The user wants to know what's wrong, not fix
it.
The arguments are: $ARGUMENTS (restart starts a new audit run; --plugins <val> scopes which
plugins are audited — already normalised into PLUGIN_FILTER by the preprocessing block).
Phases (subset of /calibrate)
- planner-init. Create the run folder; write
plan.mdwith intent"audit (read-only)",intent_source: audit-flow. - baseline-eval. Evaluator pass 1 — write
eval-features-*.md,eval-interactions-*.md,eval-intent-flow-*.md; setlast_phase_completed: baseline-eval. - Print the findings. Read
plan.mdand the three eval reports; print:- The diagnostics ask (the four CLI outputs the user must paste for exact numbers).
- Severity counts (C/H/M/L).
- The top 5 highest-impact findings, one per line:
severity · scope · feature · signature · one-line detail. - The path to the run folder so the user can read the full reports.
→ Re-run /calibrate to plan fixes, or /claude-calibration:calibration-diff after manual edits.
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.
- 10d ago First seen · 107 lines · 151 tokens per session scan A 0dbd9f6bcf3f
calibration-audit is a skill published in the GitHub repository odere-pro/claude-calibration (1 stars, last pushed 1mo ago), licensed MIT. It adds 151 tokens to every session and 1,508 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A 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
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.
writing-javascript
How browser JavaScript is written in this repo — both surfaces now speak one modern dialect and this says what that means for the code you type, where ES modules are impossible and where they are merely unused, and how to pick a feature (Baseline plus a file:// gate). Covers functional idiom over imperative DOM work…
writing-python
How Python is written in this repo — free functions over classes, structured returns instead of mutated arguments, comprehensions, no module state, and the stdlib-only, annotation-free, Python 3.8 dialect the AST lints enforce. Covers modular structure and the import-layer rule, DRY without copying a helper into a…
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.
dora-expert
DORA expert for EU financial entities. Deep knowledge of Digital Operational Resilience Act including 5 pillars, ICT risk management, incident reporting, resilience testing, third-party oversight, and information sharing for financial sector digital resilience.