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/paulbreuler/limps/mcp-code-reviewnpx skills add paulbreuler/limps --skill mcp-code-reviewgit clone --depth 1 https://github.com/paulbreuler/limpsWrote 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/paulbreuler/limps/mcp-code-review)<a href="https://agentmods.dev/skills/paulbreuler/limps/mcp-code-review"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/mcp-code-review.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.00040 | $0.00974 |
| Opus 5 | $0.00020 | $0.00487 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
mcp-code-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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP + LLM Code Review (limps)
Purpose
Perform a security-focused, test-minded code review with emphasis on MCP servers, LLM safety, and performance risks in this repository.
Scope
Use $ARGUMENTS as the scope (paths, diff range, PR number, or component name). If no scope is provided, review the current git diff.
Workflow
- Establish context
- Read
CLAUDE.mdand relevant package docs. - Identify the target package (
packages/limpsorpackages/limps-headless).
- Read
- Threat intel + dependency hygiene
- Search authoritative sources for new MCP/LLM or supply-chain issues:
- OWASP LLM Top 10, OWASP API Top 10, npm advisories, GitHub Security Advisories.
- Audit npm dependencies (use repo scripts when available):
npm audit --workspaces --include=prodnpm audit --workspaces --omit=dev(if prod-only is needed)
- Check for outdated or abandoned packages:
npm outdated --workspaces
- Inspect dependency tree for suspicious packages or name lookalikes:
npm ls --all --workspaces
- Verify lockfile integrity expectations:
- Prefer
npm cifor clean installs (verifiespackage-lock.jsonintegrity).
- Prefer
- Search authoritative sources for new MCP/LLM or supply-chain issues:
- Enumerate change surface
- List changed files and inspect diffs before diving into code.
- Security-first review
- Validate input handling, path safety, and external command usage.
- Check for secret exposure (logs, errors, telemetry).
- MCP/LLM safety review
- Review tool schemas, argument validation, and permission boundaries.
- Identify prompt injection vectors and untrusted content handling.
- Correctness and reliability
- Look for logic errors, race conditions, and edge cases.
- Performance and cost
- Identify expensive operations, redundant work, or unbounded processing.
- Tests
- Confirm coverage for new behavior and regression risk areas.
Repo-Specific Risk Areas
Focus extra scrutiny on:
packages/limps/src/server.ts,src/tools/*,src/resources/*(MCP tool/resource behavior)packages/limps/src/rlm/*andprocess_doc(s)tools (untrusted code execution)packages/limps/src/indexer.tsandsrc/watcher.ts(filesystem and database safety)packages/limps-headless/src/tools/*(external fetchers, parsing, extraction)
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 · 92 lines · 40 tokens per session scan A 40a37c70adb6
mcp-code-review is a skill published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 974 once invoked, about $0.0002 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-31.
Other skills, from other repositories
spec-init
面向新项目或现有项目的文档驱动开发 skill。Use when the user wants to create, 补齐, 更新, or refine project specs, run a Spec Kit-inspired workflow loop, maintain workflow/knowledge/change docs, analyze consistency, converge implementation back into docs, or update README/AGENTS for a real project.
release-sync
PromptHub release update skill. Use for /update-readme, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.
codex-build
Orchestrate Codex to BUILD code in the background while this Claude Code session (typically Opus) plans and reviews — never babysitting. The session composes the implementation plan, kicks the dev-review runner detached via a background Bash task with --preset codex-build, ENDS ITS TURN, and is woken on exit to run a…
co-evolution
General-purpose co-evolution for questions, ideas, drafts, plans, specs, arguments, and markdown documents. Composes or bounces content between agents using [CONTESTED]/[CLARIFY] markers until it converges. Triggers on "co-evolution", "co-evolve", "co evolve", "bounce", "bounce document", "agent bouncer", "refine with…
dev-review
Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the…
earn-hunter
Automatically monitors OKX Flash Earn, Fixed Earn and Flexible Earn opportunities, sends push notifications, and guides subscription. 自动监控 OKX 闪赚、定期和活期赚币机会，推送通知并引导申购。Use when user says: 有闪赚通知我, 监控赚币, monitor earn, notify me about earn, 定时检查理财, 执行 earn-hunter 扫描, earn-hunter scan, 活期年化高了通知我, 监控活期.