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-advisenpx skills add google/mantis --skill mantis-advisegit 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.00067 | $0.01449 |
| Opus 5 | $0.00034 | $0.00724 |
| Sonnet 5 | $0.00013 | $0.00290 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
mantis-advise scanned grade A 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 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`subprocess.run(["cmd", arg])` without `shell=True`. How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Advisor (/mantis-advise)
System Goal
Proactive Secure Development Advisor. Functions as a security guardrail and advisory assistant for developers and coding agents. Queries Mantis threat models, historical vulnerability lineages, verified remediation patterns, triaged false positives, and learned trajectory invariants to ensure that new code and refactors are implemented securely from the start.
Command Definition
- Command:
/mantis-advise - Description: Queries security knowledge for a given target file or module, evaluates proposed changes against known threat boundaries, and provides verified secure implementation guidance.
- Execution Command:
python3 reference/scripts/advise.py --file <target_file> [--db knowledge.db] - Arguments (optional):
--file/-f(or--target/-t): Target source file or component path (e.g.src/auth.pyorapi/app.py). Defaults to repo-wide scope if omitted.--db/-d: Path to Mantis SQLite database (default: auto-discoversknowledge.dborworkspace/knowledge.db).--lineage/-l: Query lifecycle and recurrence for a specific lineage UUID.--signature/-s: Query lifecycle for a specific content signature hash.--json: Emit structured JSON output instead of formatted markdown.
How to Fetch Guidance
All Mantis knowledge (threat models, historical findings, verified patches,
triaged false positives, and learned invariants) lives in the SQLite database
(knowledge.db). Do not look for flat files on disk (like learnings.jsonl or
workspace/findings/*.json). Use one of the two execution doors below:
Mechanism 1: CLI Execution (Recommended for Coding Agents)
Coding agents with standard bash access should run
reference/scripts/advise.py:
-
Query Security Guidance for Target File:
python3 reference/scripts/advise.py --file src/auth.pyPrints: Actionable security advisory markdown with active threat model, historical vulnerabilities, verified patch diffs, triaged false positives, and invariants.
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 · 180 lines · 67 tokens per session scan A 026e82fe6573
mantis-advise is a skill published in the GitHub repository google/mantis (853 stars, last pushed 5d ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,449 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). 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.