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 calibrate-rulesgit 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/calibrate-rules)<a href="https://agentmods.dev/skills/odere-pro/claude-calibration/calibrate-rules"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibrate-rules/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/calibrate-rules"><img src="https://agentmods.dev/badge/skills/odere-pro/claude-calibration/calibrate-rules.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.00166 | $0.01178 |
| Opus 5 | $0.00083 | $0.00589 |
| Sonnet 5 | $0.00033 | $0.00236 |
| Haiku 4.5 | $0.00017 | $0.00118 |
Grade A, and why
calibrate-rules 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
calibrate-rules — per-feature bundle
You audit and tune .claude/rules/ files. You receive one of two kinds of work:
- Direct invocation (
/claude-calibration:calibrate-rules) — audit everything, report findings, propose fixes inline. The user drives the conversation. - Dispatch from the calibrator — one approved plan row at a time, applied surgically.
In both cases the workflow is the same; only the framing differs.
1. Enumerate
bash <BUNDLE>/scripts/enumerate.sh "$PROJECT_DIR"
Yields TSV scope\tpath. Scope is user (~/.claude/rules/...), project
(<PROJECT_DIR>/.claude/rules/...), or plugin-self (<plugin-root>/rules/... when the project
itself is a plugin).
2. Lint
bash <BUNDLE>/scripts/lint.sh <path …>
Yields TSV path\tsignature\tseverity\tdetail. The signatures this bundle owns
(see reference.md):
rule:secret-leak(CRITICAL)rule:over-200(MEDIUM)rule:no-paths-when-language-specific(MEDIUM)rule:plugin-shipped-no-paths(HIGH)rule:bad-glob(HIGH)rule:contradicts-claude-md(LOW)rule:should-be-skill(LOW)
3. Fix — kind: edit rows
For each finding, the remediation pattern is in examples/<case>/:
rule:over-200→examples/over-200/{before,after}.md(split into focused files)rule:no-paths-when-language-specific→examples/no-paths/{before,after}.md(add frontmatter with apaths:list)rule:plugin-shipped-no-paths→ same fix asno-pathsplus a note that the rule ships to every user who enables the plugin.rule:secret-leak→ remove the secret, rotate it, add to.gitignoreor move to.local.rule:bad-glob→ fix the YAML list shape.rule:contradicts-claude-md→ reconcile: move the canonical statement to one place, link from the other.rule:should-be-skill→ propose a new skill at.claude/skills/<name>/SKILL.md; remove the rule file or leave it as a one-line pointer.
4. Create — kind: create rows
When the planner detects a recurrence that this bundle owns (per rules/dispatch.md):
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 96 lines · 166 tokens per session scan A e3640754d456
calibrate-rules is a skill published in the GitHub repository odere-pro/claude-calibration (1 stars, last pushed 1mo ago), licensed MIT. It adds 166 tokens to every session and 1,178 once invoked, about $0.0008 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.