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-threat-modelnpx skills add google/mantis --skill mantis-threat-modelgit 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.00059 | $0.03281 |
| Opus 5 | $0.00030 | $0.01640 |
| Sonnet 5 | $0.00012 | $0.00656 |
| Haiku 4.5 | $0.00006 | $0.00328 |
Grade A, and why
mantis-threat-model 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Threat Modeler (/mantis-threat-model)
System Goal
Security Architect. Synthesizes trust boundaries, attack surfaces, and attacker
profiles into THREAT_MODEL.md based exclusively on the entities and
architecture defined in the Knowledge Base (KB).
Command Definition
- Command:
/mantis-threat-model - Description: Evaluates architectural perimeters, entry points, and trust boundaries to construct the threat model.
- Arguments (all optional; absent → today's behavior):
--state_root <dir>: parent ofworkspace/. If absent, use./workspace/...relative to the current directory. Locates.mantis_state.json, the KB, and the archive directory.--snapshot_id <id>: theSNAPSHOT_IDthis pass is pinned to. Used ONLY as the provenance value stamped intoTHREAT_MODEL.md(theKB_SNAPSHOT:line). If absent, fall back toactive_snapshot.snapshot_idfrom state; if that is also absent orsnapshot_pinnedis false, the stamp is the literalUNPINNED.--snapshot_root <dir>: accepted for interface uniformity but NOT used — this stage never reads target source (Block A step 0, findings-only role).
Input/Output Contract
- Reads:
workspace/.mantis_state.json—pass_number(to archive per pass) and, for provenance only,active_snapshot({root, snapshot_id, snapshot_pinned}). Both optional; absent → degraded (see Backward-compat).workspace/kb/architecture.md.workspace/kb/entities/*.md.- The EXISTING
workspace/kb/THREAT_MODEL.mdfrom the previous pass, if present — only its firstKB_SNAPSHOT:line, for the freshness check in step 0.
- Writes:
workspace/kb/THREAT_MODEL.md(first line is aKB_SNAPSHOT:provenance header).- Archives the previous
workspace/kb/THREAT_MODEL.md(if any) toworkspace/archive/kb/THREAT_MODEL_pass_${N}.mdBEFORE overwriting.
- Preconditions:
- Knowledge Base files must exist and be populated.
- Idempotency Guarantee:
- Copies the prior
THREAT_MODEL.md(if any) to the pass archive, then deterministically overwritesworkspace/kb/THREAT_MODEL.mdin-place. Re-running a pass with an unchanged snapshot reproduces an equivalent model plus aSTALEbanner (see step 0 and the final save step).
- Copies the prior
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 · 252 lines · 59 tokens per session scan A ced15d440489
mantis-threat-model is a skill published in the GitHub repository google/mantis (853 stars, last pushed 5d ago), licensed Apache-2.0. It adds 59 tokens to every session and 3,281 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.