mcp-everything-search: Skill for Claude Code

.claude/skills/maid-run-review/SKILL.md

maid-run-review is a skill for Claude Code from mamertofabian/mcp-everything-search. It costs 20 tokens per session (719 once invoked), scanned A, original, MIT.

An optional review workflow for a completed MAID run, using a language model outside the deterministic MAID runner. The resulting report is advisory and includes a disclosure when run evidence is sent to a cloud provider.

In plain words
What is it for?
Use it to create, validate, and render a review of run findings, plan evidence, lessons, incidents, notes, and an optional diff file.
Why use it?
It separates model-based commentary from the runner so the core run remains reproducible, while making the privacy boundary clear.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is mamertofabian/mcp-everything-search's own configuration. It tells Claude Code how to work on mcp-everything-search itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-everything-search configures →

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-run-review/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.

agentmods badge for maid-run-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-run-review/github.svg)](https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-run-review)
Your own site
<a href="https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-run-review"><img src="https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-run-review/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 maid-run-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/mamertofabian/mcp-everything-search/maid-run-review"><img src="https://agentmods.dev/badge/skills/mamertofabian/mcp-everything-search/maid-run-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 719 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00719
Opus 5.5 $0.00008 $0.00288
Sonnet 5.5 $0.00004 $0.00144
Haiku 4.5 $0.00002 $0.00072

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

Security

Grade A, and why

maid-run-review 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-run-review/SKILL.md · 85 lines

How it starts

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

MAID Run Review

Generate an optional LLM-assisted review of one completed MAID run while keeping maid-runner itself deterministic and AI-free. This skill is the only place in the run-review workflow that may call a model or touch provider credentials.

Rules

  • Keep runner commands deterministic. Use maid evaluate only for run evidence, prompt request creation, review validation, and markdown rendering.
  • Use the model access already available to the hosting agent, or a specific model the user chooses.
  • CLOUD-PRIVACY: before using a cloud model, disclose that the bounded run review request leaves the machine. Name what run evidence leaves the machine: deterministic evaluation findings, plan-lock revision evidence, Outcome lessons and review notes, incident counts, and any operator-supplied diff file included with --diff-file.
  • A non-zero review validation result is a hard stop. Do not hand-edit citations or evidence ids to satisfy validation; regenerate the candidate review from the bounded request instead.
  • The final report is advisory, never a gate. It must not be fed back to the implementing agent as instructions during an active run.
  • Use only registered maid evaluate options. Do not invent provider, model, base URL, timeout, or API-key options for maid-runner.

Workflow

  1. Show the deterministic run evidence first:

    maid evaluate run <manifest>
    
  2. Build the bounded review request:

    maid evaluate prompt <manifest> --output .maid/run-review-request.json
    

    If the operator wants diff evidence included, prepare a diff file explicitly, say how it was prepared, and pass it through the existing option:

    maid evaluate prompt <manifest> --diff-file <diff-file> --output .maid/run-review-request.json
    
  3. Generate a candidate review with an agent-available model.

    Send only .maid/run-review-request.json to the model. If that uses a cloud model, disclose CLOUD-PRIVACY first and name what run evidence leaves the machine. The model output must be a JSON run review that cites only evidence ids from the request.

Read the full file on GitHub · 85 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. 11d ago First seen · 85 lines · 20 tokens per session scan A 074f230dc3d7

Subscribe to this mod's changes

maid-run-review is a skill published in the GitHub repository mamertofabian/mcp-everything-search (367 stars, last pushed 12d ago), licensed MIT. It adds 20 tokens to every session and 719 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

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