Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Borda/AI-Rig/plugin install foundryWrote 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/borda/ai-rig/calibrate)<a href="https://agentmods.dev/skills/borda/ai-rig/calibrate"><img src="https://agentmods.dev/badge/skills/borda/ai-rig/calibrate.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.00047 | $0.12118 |
| Opus 5 | $0.00023 | $0.06059 |
| Sonnet 5 | $0.00009 | $0.02424 |
| Haiku 4.5 | $0.00005 | $0.01212 |
Grade B, and why
calibrate 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 today.
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.
OSS_AVAILABLE=$(find ~/.claude/plugins/cache -name "oss" -type d 2>/dev/null | head -1) # timeout: 5000 How it starts
The opening of the file, as written. The whole thing — 544 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate agents and skills by measuring outputs against synthetic problems with defined ground truth. Primary signal: calibration bias — gap between self-reported confidence and actual recall. Well-calibrated agent reports 0.9 when it finds ~90% of issues. Miscalibrated: reports 0.9, finds 60%.
Calibration data drives improvement loop: systematic gaps → instruction updates; persistent overconfidence → adjusted re-run thresholds in MEMORY.md.
NOT for: static routing overlap analysis (use /foundry:audit); manually reviewing skill output quality (use /develop:review (requires develop plugin)).
-
$ARGUMENTS: parse
--flagsfirst, then resolve remaining tokens as scope targetsFlags (order independent):
--fast— 3 problems per target (default when neither pace flag passed)--full— 10 problems per target; mutually exclusive with--fast--ab-test— also rungeneral-purposebaseline and report delta metrics; requires benchmark (default--fastif no pace flag); mutually exclusive with--apply--apply— apply proposals: with--fast/--full: run benchmark then immediately apply; without pace flag: skip benchmark, apply proposals from most recent past run; mutually exclusive with--ab-test--skip-gate— suppress follow-up gate; for programmatic callers--local— resolve target agent/skill files from source tree (plugins/*/) instead of installed plugin cache; for plugin-dev workflows where local edits aren't yet installed; setsLOCAL_MODE=truein all pipeline spawns
Mutual exclusion validation (check before any work):
--ab-test+--applytogether → hard error: "--ab-testand--applyare mutually exclusive. Pass one or neither."--fast+--fulltogether → hard error: "Pass--fastor--full, not both."--ab-testwithout pace flag → default--fastsilently (no error)
Unsupported flag check — after all supported flags extracted (
--fast,--full,--ab-test,--apply,--skip-gate,--local,--keep), scan$ARGUMENTSfor remaining--<token>tokens. If found: print! Unknown flag(s): `--<token>`. Supported: `--fast`, `--full`, `--ab-test`, `--apply`, `--skip-gate`, `--local`, `--keep`.then invokeAskUserQuestion— (a) Abort (stop, re-invoke with correct flags) · (b) Continue ignoring (skip unknown flags, proceed). On Abort: stop.Legacy positional tokens (
ab,apply,fast,full) — hard error: print migration hint and stop. Example: "abremoved — use--ab-testflag:/calibrate curator --ab-test."Scope tokens (positional, space-separated — defaults to
all):all— all agents + relevant skills + routing + communication + all rulesagents— all agents only (full agent list inmodes/agents.md)skills— calibratable skills only (/auditand others permodes/skills.md;/oss:review(requiresossplugin) excluded — requires live GitHub PR)routing— routing accuracy test: measures how accuratelygeneral-purposeorchestrator selects correctsubagent_typefor synthetic task prompts (not per-agent quality benchmark; included inall)communication— handover + team protocol compliance: runsfoundry:curatoragainst synthetic agent responses and team transcripts with injected protocol violations (missing JSON envelope, missingsummary, AgentSpeak v2 breaches); included inallrules— rule adherence test: for each global rule file (nopaths:) and each path-scoped rule when matching file is in context, generates synthetic tasks that should trigger rule's key directives, measures whethergeneral-purposeagent with rule loaded correctly applies them; reports rules that are ignored, misapplied, or redundant; included inallplugins— all agents + calibratable skills from allplugins/*/directories (union of all plugin-namespaced agents and calibratable skills)<plugin-name>— tier 2: bare plugin directory name (e.g.oss,foundry,research,develop) auto-resolved when token matchesplugins/<name>/directory; calibrates all agents + calibratable skills in that plugin<agent-name>— tier 3: single agent (e.g.,foundry:sw-engineer); also accepts bare name (e.g.sw-engineer) and resolves viaplugins/*/agents/<name>.md/foundry:audit— single skill (pass any calibratable skill name;/oss:review(requiresossplugin) accepted but excluded permodes/skills.md)- Multiple scope tokens — space-separated; calibrates union of resolved targets:
oss research,agents skills,curator shepherd; each token resolved through same tier hierarchy as/auditscope tokens (reserved keywords first, then plugin-dir lookup, then agent/skill file search)
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.
- today Changed 8e88eae77d01
- 7d ago First seen · 544 lines · 47 tokens per session scan B 244c1a762286
calibrate is a skill published in the GitHub repository Borda/AI-Rig (26 stars, last pushed yesterday), licensed Apache-2.0. It adds 47 tokens to every session and 12,118 once invoked, about $0.0002 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-30.
Other skills, from other repositories
endpoint-probe
Probes each major Agent Monitor API route — /api/stats, /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/runs, /api/cc-config/overview — and reports each one's HTTP status, latency, and response shape, flagging which are reachable. Use to verify a dashboard install is wired up correctly.
auto-test-code
A structured process for critically reviewing and testing software code. It records review findings, test plans, commands, results, and supporting files in a project workspace.
auto-test-skill
A structured process for critically testing and improving a coding skill. It records test plans, findings, fixes, and quality checks in files that can be reviewed later.
auto-test-project
A structured process for testing and improving a complete software project. It runs repeated critical tests and broader quality checks across the project.
tdd-workflow
A test-first development workflow, commonly called TDD, where a failing test is written before the code that should make it pass. The cycle then adds the smallest working change and cleans it up.
laravel-testing
Use when testing controllers, services, or models, or implementing TDD on Laravel 13 with Pest 4 / PHPUnit 12.