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/google/mantis/mantis-calibratenpx skills add google/mantis --skill mantis-calibrategit clone --depth 1 https://github.com/google/mantisWhat 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 | $0.00052 | $0.09989 |
| Opus 5 | $0.00026 | $0.04994 |
| Sonnet 5 | $0.00010 | $0.01998 |
| Haiku 4.5 | $0.00005 | $0.00999 |
Grade A, and why
mantis-calibrate 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 3d 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 — 667 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Risk Calibrator (/mantis-calibrate)
System Goal
Risk Analysis Expert. Evaluates confirmed findings against a rigorous risk matrix, taking into account successful reproduction and production viability to produce a final risk score (1-10).
Command Definition
- Command:
/mantis-calibrate - Description: Calibrates the risk level of findings based on evidence and impact.
Input/Output Contract
- Reads:
workspace/findings/*.json(all finding files to load full pipeline state).workspace/kb/THREAT_MODEL.md(if exists, to check threat boundary overrides and asset criticality).workspace/.mantis_state.json(to track the current loop pass, and to readactive_snapshot—{snapshot_id, snapshot_pinned, root}— for finding provenance and history stamping; absent ⇒ degraded/today's behavior).
- Writes:
- Updates finding files in-place with scoring/calibration fields
(
impact_score,likelihood_score,availability_tier,inferred_exposure,attacker_position,mantis_risk_score,priority,sanity_triage_applied(may begin withSTALE_EVIDENCEwhen the STALE-EVIDENCE guard suppresses heuristics),calibration_checklist(entries may carrySTALE_EVIDENCE:reasons),outrage_commentary,executive_summary). Appends ahistoryentry withsnapshotprovenance (see history JSON template in the body). - Reusable helper script
workspace/helpers/append_calibrate.py.
- Updates finding files in-place with scoring/calibration fields
(
- Preconditions:
- Confirmed or raw findings must exist in
workspace/findings/.
- Confirmed or raw findings must exist in
- Idempotency Guarantee:
- Updates findings in place by overwriting existing keys with the calculated score. Running multiple times on the same inputs yields identical outputs, with no duplicated entries.
Instructions
Convert the raw security findings and their empirical results (repro/patch) into a prioritized, actionable risk report.
Execute the calibration as follows:
Locator resolution (findings-only). Calibrate never needs to read target source to compute a score, but some heuristics below may re-inspect code; resolve the code root the same way every stage does. Block A is inlined below:
What ships with it
1 file 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.
- 3d ago First seen · 667 lines · 52 tokens per session scan A c4eb14c114e3
mantis-calibrate is a skill published in the GitHub repository google/mantis (853 stars, last pushed 5d ago), licensed Apache-2.0. It adds 52 tokens to every session and 9,989 once invoked, about $0.0003 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-30.
Other skills, from other repositories
conductor-setup
Scaffolds the project and sets up the Conductor environment. Use this whenever a project needs to be initialized or if the Conductor configuration is missing.
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
conductor-review
Reviews the completed track work against guidelines and the plan. Acts as a Principal Software Engineer to ensure quality and compliance.
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
conductor-revert
Reverts previous work (tracks, phases, or tasks) by identifying associated commits and performing Git reverts.
conductor-status
Displays the current progress of the project by parsing the Tracks Registry and individual track plans.