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-historynpx skills add google/mantis --skill mantis-historygit clone --depth 1 https://github.com/google/mantisWrote 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/google/mantis/mantis-history)<a href="https://agentmods.dev/skills/google/mantis/mantis-history"><img src="https://agentmods.dev/badge/skills/google/mantis/mantis-history.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 | $0.00076 | $0.02952 |
| Opus 5 | $0.00038 | $0.01476 |
| Sonnet 5 | $0.00015 | $0.00590 |
| Haiku 4.5 | $0.00008 | $0.00295 |
Grade A, and why
mantis-history 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 4d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
History Analyzer (/mantis-history)
System Goal
Historical Vulnerability Extractor. Analyzes repository's version control system (VCS) history to extract past vulnerabilities, security-related fixes, patches, and associated files, creating a historical learnings database to inform downstream skills.
Command Definition
- Command:
/mantis-history - Description: Analyzes repository's version control system (VCS) history to
extract past vulnerabilities and fixes, producing a structured historical
learnings file (
workspace/historical_learnings.jsonl). - Arguments (optional; supplied by the orchestrator, consumed by Block A):
--snapshot_root/--snapshot_id/--state_root. History reads VCS logs from the LIVE repository root (Block A step 5), not the snapshot; it uses--state_rootonly to place its cache/output/script. All absent -> DEGRADED (behaves as today, live cwd).
Input/Output Contract
- Reads:
workspace/.mantis_state.json(to track current loop pass).- Codebase directory structure and key files (to determine stack).
- VCS history logs (commit messages, titles, diffs).
mantis-summary.md(optional, if available).- Internal history analysis cache (optional, if exists).
- Writes:
- VCS extraction script (written on-the-fly to workspace).
workspace/historical_learnings.jsonl.- Internal history analysis cache.
- All under
--state_root/workspace/(cache,historical_learnings.jsonl, extraction script): kept outside the target tree. Optionalhistory_statusmarker (UNSUPPORTED_VCS/PARTIAL_SHALLOW).
- Preconditions:
- Target repository and VCS logs must be accessible.
- Idempotency Guarantee:
- The cache is the source of truth: the output DB is rebuilt from it every run
and is never truncated to empty while the cache is non-empty. The cache is
invalidated on VCS-history rewrite (
_analyzed_headno longer reachable) or a vcs_type/repo-identity change. Onnone/unknownVCS the stage writes an empty DB +history_status=UNSUPPORTED_VCSand exits.
- The cache is the source of truth: the output DB is rebuilt from it every run
and is never truncated to empty while the cache is non-empty. The cache is
invalidated on VCS-history rewrite (
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.
- 4d ago First seen · 240 lines · 76 tokens per session scan A ef777063f09b
mantis-history is a skill published in the GitHub repository google/mantis (853 stars, last pushed 6d ago), licensed Apache-2.0. It adds 76 tokens to every session and 2,952 once invoked, about $0.0004 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.