mantis-reflect

mantis-reflect is a skill for Claude Code, Codex from google/mantis. It costs 56 tokens per session (2,545 once invoked), scanned A, original, Apache-2.0.

A step that examines an AI agent’s recorded work, including its messages, tool calls, and results, then saves useful lessons in a JSON Lines file. JSON Lines stores one JSON record per line.

In plain words
What is it for?
Use it at the end of a Mantis run to analyze execution logs and append structured learnings to workspace/learnings.jsonl.
Why use it?
It captures successes, failures, and incorrect assumptions so later agents can avoid repeating the same mistakes.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Claude Code; mentions Gemini CLI.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is --state_root if passed, else ./workspace/... relative to the current dir).

Good fit Use it at the end of a Mantis run to analyze execution logs and append structured learnings to workspace/learnings.jsonl.

Compare 6 skills from other repositories ↓
About the project

google/mantis is a modular set of security-review skills that coding agents use to find, reproduce, and patch software vulnerabilities. It is for adapting automated security testing to application, infrastructure, machine-learning, hardware, and firmware projects, with expert review required for results. The catalogue skills and instruction provide the workflow for using Mantis with coding agents.

google/mantis · 2,525 stars · on GitHub · cloud.google.com

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/google/mantis
agentmods
npx agentmods add skills/google/mantis/mantis-reflect

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mantis-reflect

README.md
[![agentmods](https://agentmods.dev/badge/skills/google/mantis/mantis-reflect/github.svg)](https://agentmods.dev/skills/google/mantis/mantis-reflect)
Your own site
<a href="https://agentmods.dev/skills/google/mantis/mantis-reflect"><img src="https://agentmods.dev/badge/skills/google/mantis/mantis-reflect/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for mantis-reflect

Your own site · 80×15
<a href="https://agentmods.dev/skills/google/mantis/mantis-reflect"><img src="https://agentmods.dev/badge/skills/google/mantis/mantis-reflect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,545 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket pass 14 Sept 2026
  • Snyk pass 14 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.02545
Opus 5.5 $0.00022 $0.01018
Sonnet 5.5 $0.00011 $0.00509
Haiku 4.5 $0.00006 $0.00254

Measured 1mo ago against content hash cd9b985a9199, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mantis-reflect 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 1mo 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.

skills/mantis-reflect/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reflector (/mantis-reflect)

System Goal

Execution Trajectory Analyst. Analyzes the sequence of thoughts, tool calls, and observations (the "trajectory" or "conversation") of the other Mantis agents. Extracts valuable insights to prevent future agents from making the same mistakes.

Command Definition

  • Command: /mantis-reflect
  • Description: Parses execution trajectories from the current loop and appends structured insights to workspace/learnings.jsonl.

Input/Output Contract

  • Reads:
    • workspace/.mantis_state.json (to track the current loop pass, and to read active_snapshot.snapshot_id for provenance stamping — see Instructions step 3). Read this file STATE-RELATIVE under --state_root; never derive snapshot state by running live VCS.
    • Subagent execution logs (transcript.jsonl files). The schema execution_log_entry defined in schema.json is the normalized representation. The orchestrator/adapter must normalize raw logs from unsupported frameworks before passing them, or the reflector must parse unsupported formats on a best-effort basis.
    • Locating Logs (harness-neutral): The orchestrator SHOULD pass the list of absolute file paths to the execution log files (e.g. transcript.jsonl) for the subagents executed during this round; when provided, use these paths directly. Do NOT hardcode any single framework's log layout. If no path list was passed, resolve transcript paths from the ACTIVE harness's own transcript convention — this is harness-specific and there are several. For example, Antigravity stores them under <appDataDir>/brain/<conversation_id>/.system_generated/logs/transcript.jsonl; other harnesses (e.g. Gemini CLI, the Google ADK, Claude Code) use different layouts. Antigravity is ONE example among several, not the default. If, after both routes, no readable transcript exists for a stage that ran this round, do NOT abort and do NOT silently emit zero learnings — record a missing-transcript insight per Instructions step 1.
  • Writes:
    • Appends structured trajectory insights to workspace/learnings.jsonl.
  • Preconditions:
    • Execution logs for the current round SHOULD exist and contain entries. If a stage's log is missing, unreadable, empty, or yields zero parseable entries, this is NOT a fatal error and NOT a reason to stop: continue with the other stages and record the gap as a trajectory_insight (see Instructions step 1) so an absent log is never a silent zero-learnings result.
  • Idempotency Guarantee:
    • Parses logs and filters already-recorded learnings to prevent duplicate entries in workspace/learnings.jsonl. It should check existing lines in workspace/learnings.jsonl to ensure it doesn't duplicate the same insight if retried.
    • When de-duplicating, compare on the semantic content (target_entity + insight + source_stage) and treat snapshot as attached metadata, NOT part of the identity, so a retry within the same pass does not double-append. Missing-transcript insights (step 1) are de-duplicated the same way.

Read the full file on GitHub · 188 lines

Changes

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.

  1. 1mo ago First seen · 188 lines · 56 tokens per session scan A cd9b985a9199

Subscribe to this mod's changes

mantis-reflect is a skill published in the GitHub repository google/mantis (2,525 stars, last pushed today), licensed Apache-2.0. It adds 56 tokens to every session and 2,545 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

ai-engineering-toolkit

Overview of six AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.

sickn33/agentic-awesome-skills · 47 tokens

ai-agent-evaluation-benchmarking

Autonomous AI agent benchmark evaluation register: task completion rates, planning accuracy, tool invocation precision, and cost benchmarks.

sickn33/agentic-awesome-skills · 31 tokens

ai-agent-tool-routing

Use when designing or reviewing an AI agent tool registry or MCP router: document parameter schemas, caller authorization, execution limits, replay-safe retries and verification evidence.

sickn33/agentic-awesome-skills · 36 tokens

jobs

Manage agy staffer background jobs - collect results, check status, cancel, follow-up conversation, and setup. Use when an agy job needs collecting, when the user asks "is the agy job done", "show agy's result", "cancel the agy job", "continue the agy conversation", or "set up agy". This is the orchestrator's skill…

keli-wen/agy-staff · 99 tokens

agy-lead

Orchestrate an ongoing task with AGY while the current agent owns key decisions, review, and delivery. Use when the user invokes /agy-lead or asks you to coordinate a task using AGY.

keli-wen/agy-staff · 46 tokens

researcher

Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.

keli-wen/agy-staff · 75 tokens