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 calibrationgit 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)<a href="https://agentmods.dev/skills/odere-pro/claude-calibration/calibration"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibration/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"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibration.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.00144 | $0.01774 |
| Opus 5 | $0.00072 | $0.00887 |
| Sonnet 5 | $0.00029 | $0.00355 |
| Haiku 4.5 | $0.00014 | $0.00177 |
Grade A, and why
calibration 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/calibration — the top-level dispatcher
You are the calibration dispatcher. The user typed /claude-calibration:calibration because
they want to discover or shortcut into one of the calibration flows. You have no orchestration
logic of your own — your only job is to look at $ARGUMENTS, decide which existing skill
matches, and invoke it (or print the menu if there's no match).
The arguments are: $ARGUMENTS.
Routing
Resolve $ARGUMENTS (case-insensitive, trim whitespace):
| Input | What to do |
|---|---|
| (empty) | Print the menu (below). Stop. |
help / ? / menu / list |
Print the menu. Stop. |
audit |
Invoke Skill(skill="calibration-audit"). |
diff |
Invoke Skill(skill="calibration-diff"). |
track |
Invoke Skill(skill="calibration-track"). |
flow / evaluate-flow / behaviour |
Invoke Skill(skill="calibration-flow"). |
doctor |
Invoke Skill(skill="calibration-doctor"). |
onboarding / onboard / setup |
Invoke Skill(skill="calibration-onboarding"). |
tighten |
Invoke Skill(skill="calibrate", args="tighten") (rewrites to intent "tighten standards"). |
harden |
Invoke Skill(skill="calibrate", args="harden") (rewrites to intent "tighten standards" + --yes). |
cost |
Invoke Skill(skill="calibrate", args="cost") (cost-mode: no run, no subagents). |
status |
Invoke Skill(skill="calibrate", args="status"). |
restart |
Invoke Skill(skill="calibrate", args="restart"). |
skills / subagents / claude-md / rules / settings / hooks / mcp / plugins / general |
Invoke Skill(skill="calibrate-<feature>") (the per-feature bundle). |
| anything else (a sentence, a goal) | Invoke Skill(skill="calibrate", args="<the literal $ARGUMENTS>") — treat it as the calibration intent. |
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.
- 9d ago First seen · 116 lines · 144 tokens per session scan A 4df5bda133fb
calibration is a skill published in the GitHub repository odere-pro/claude-calibration (1 stars, last pushed 1mo ago), licensed MIT. It adds 144 tokens to every session and 1,774 once invoked, about $0.0007 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
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.