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-reportnpx skills add google/mantis --skill mantis-reportgit 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.00044 | $0.06175 |
| Opus 5 | $0.00022 | $0.03087 |
| Sonnet 5 | $0.00009 | $0.01235 |
| Haiku 4.5 | $0.00004 | $0.00617 |
Grade A, and why
mantis-report 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 2d 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporter (/mantis-report)
System Goal
Security Reporting Expert. Synthesizes complex, technical finding logs into a high-quality, human-readable review packet for developers and stakeholders.
Command Definition
- Command:
/mantis-report - Description: Generates a human-readable security review packet containing confirmed findings and exploit chains.
Input/Output Contract
- Reads:
workspace/findings/*.json(all active finding files for this pass).workspace/archive/findings_pass_*/*.json(archived findings from prior passes) and legacyworkspace/archive/loop*_findings/*.json. The report is a campaign-wide view: this pass's full findings plus carried-forward findings that prior passes stopped retrying (e.g. hit the retry cap) so they do not vanish from the report.workspace/.mantis_state.json(to track current loop pass, and to readvcs_infoandactive_snapshot{root,snapshot_id,snapshot_pinned} for provenance).- Per-finding snapshot provenance fields, all OPTIONAL:
discovery_commit,repro_snapshot_id,patch_base_snapshot. When any is absent/empty it is rendered as "(not recorded)" — never a reason to drop a finding.
- Writes:
workspace/report/review_packet_pass_<N>_<snapshot_tag>.md(pass- and snapshot-tagged markdown report). Falls back to the unsuffixedreview_packet_pass_<N>.mdon a legacy pass with no recorded snapshot.- Updates copy/symlink at
workspace/report/review_packet-latest.md.
- Preconditions:
- Calibrated and reproduced findings exist in
workspace/findings/orworkspace/archive/. The report is a campaign-wide view: it reports the current state of every unresolved finding discovered in this or any prior pass, de-duplicated to each finding's latest state. A confirmed-but-unfixed finding that plan stopped carrying back (e.g. it hit the 2-attempt retry cap) does NOT vanish — it appears here at its most recent archived state.
- Calibrated and reproduced findings exist in
- Idempotency Guarantee:
- Writes to pass-and-snapshot-tagged files. In-place overwrite of
review_packet-latest.md. Re-running the SAME pass on the SAME snapshot updates the same tagged file. Re-running the same pass number on a DIFFERENT snapshot writes a DISTINCT file (the<snapshot_tag>suffix prevents cross-snapshot overwrite). Legacy passes with no recorded snapshot keep the unsuffixedreview_packet_pass_<N>.mdname and overwrite in place, exactly as before.
- Writes to pass-and-snapshot-tagged files. In-place overwrite of
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.
- 2d ago First seen · 418 lines · 44 tokens per session scan A c80192b51c35
mantis-report is a skill published in the GitHub repository google/mantis (853 stars, last pushed 5d ago), licensed Apache-2.0. It adds 44 tokens to every session and 6,175 once invoked, about $0.0002 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.