What is maid-incident-logger?

A record-keeping workflow for MAID incidents, where MAID is a system for tracking how coding agents plan and perform work. It saves human-selected examples of model gaming or implementation drift, along with evidence and chosen or rejected changes.

Use it to capture and list incidents, update them with chosen changes, and export chosen/rejected examples for DPO training, a method for improving models from preferred and rejected outputs.

It keeps incident records consistent and reproducible instead of relying on hand-written files or undocumented judgments.

How mamertofabian/mcp-everything-search configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to mamertofabian/mcp-everything-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mamertofabian/mcp-everything-search/main/.claude/skills/maid-incident-logger/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/mamertofabian/mcp-everything-search

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-incident-logger/github.svg)](https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-incident-logger)

Your own site

<a href="https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-incident-logger"><img src="https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-incident-logger/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-incident-logger"><img src="https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-incident-logger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 742 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00064	$0.00742
Opus 5.5	$0.00026	$0.00297
Sonnet 5.5	$0.00013	$0.00148
Haiku 4.5	$0.00006	$0.00074

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

Security

Grade A, and why

maid-incident-logger 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 11d 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.

.claude/skills/maid-incident-logger/SKILL.md · 75 lines

How it starts

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

MAID Incident Logger

Create a human-curated incident record through MAID's deterministic incident commands. A human or agent decides that an event was a gaming attempt; MAID records and retrieves the supplied evidence deterministically. No inference, classification models, or hidden summarization are involved.

Incident records are YAML files under the repository-local .maid/incidents/ directory. Do not hand-write incident files, invent metadata fields, or document any unshipped behavior. The skill guidance must add no new CLI behavior.

Deterministic Incident Commands

Use only the shipped command surface:

maid incident capture --manifest <path> --packet <path> --rejected-diff <path> --tags <comma-list> [--notes <text>]
maid incident update <incident-path> --chosen-diff <path>
maid incident list [--tag <tag>] [--json]
maid incident export --format dpo --output <path>
maid incident suggest-temptations --paths <comma-list> [--json]

Capture Workflow

When a contract-integrity gate catches a gaming attempt, capture the incident immediately with the failure packet and rejected diff:

maid incident capture --manifest <path> --packet <path> --rejected-diff <path> --tags <comma-list> [--notes <text>]

Then update the same incident after the honest fix lands by attaching the chosen diff:

maid incident update <incident-path> --chosen-diff <path>

Use maid incident list [--tag <tag>] [--json] to inspect stored records. Use maid incident export --format dpo --output <path> only after records have chosen diffs. Use maid incident suggest-temptations --paths <comma-list> [--json] to surface deterministic advisory temptation entries for future manifests.

Pattern Tags

Use the closed pattern-tag vocabulary exactly:

test-weakening
trivial-test
stub-implementation
contract-renegotiation
scope-escape
runner-gaming
false-done

Unknown tags are rejected as a usage error. Vocabulary changes require a manifest evolution.

Read the full file on GitHub · 75 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.

11d ago First seen · 75 lines · 64 tokens per session scan A be8633e91675

Subscribe to this mod's changes

maid-incident-logger is a skill published in the GitHub repository mamertofabian/mcp-everything-search (367 stars, last pushed 12d ago), licensed MIT. It adds 64 tokens to every session and 742 once invoked, about $0.0003 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-10-18.

Building agents

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

mcp-everything-search: Skill for Claude Code