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 agents/paulbreuler/limps/002_agent_cleanupgit 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/agents/paulbreuler/limps/002_agent_cleanup)<a href="https://agentmods.dev/agents/paulbreuler/limps/002_agent_cleanup"><img src="https://agentmods.dev/badge/agents/paulbreuler/limps/002_agent_cleanup.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.1 | $0.00000 | $0.00851 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00170 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
002_agent_cleanup 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent 2: Cleanup — Remove serve, bump v3
Plan Location: plans/0049-persistent-http-server/0049-persistent-http-server-plan.md
Scope
Features: #6
Own: src/commands/serve.tsx (delete), src/cli.tsx, package.json
Depend on: Agent 0 + Agent 1 (start/stop must work before removing serve)
Block: Nothing
Interfaces
Receive (from Agent 0, Agent 1) ✅ READY when both are PASS
// Agent 1 provides working start/stop commands
// src/commands/start.tsx — replaces serve
// src/commands/stop.tsx — new
Features
#6: Remove limps serve and update CLI
TL;DR: Delete serve command, remove CLI bypass hack, bump to v3, add express dep.
Status: GAP
Files: src/commands/serve.tsx (delete), src/cli.tsx (modify), package.json (modify)
Steps:
- Delete
src/commands/serve.tsx - Modify
src/cli.tsx— remove the serve bypass block (lines ~8-22 that detectserveinprocess.argvand callstartMcpServer()directly bypassing Pastel). Thestartcommand doesn't need this hack because it uses HTTP transport, not stdio. - Modify
packages/limps/package.json:"version": "3.0.0"- Add
"express": "^5.0.1"todependencies - Add
"@types/express": "^5"todevDependencies
- Update any references to
servein help text, descriptions, or other commands (e.g.,configcommand mentions serve) - Check
src/index.ts— if it callsstartMcpServer()for backward compat, update or remove
TDD:
serve is not a valid command→ runlimps serve→ assert error or helpful message pointing tolimps startstart appears in help output→ runlimps --help→ assertstartandstoplistedbuild succeeds without serve→npm run build→ assert clean compilation
Gotchas:
src/index.tsis a backward-compat entry for"bin"— may need updating to launch HTTP server instead of stdio- Check
src/cli/config-cmd.tsfor serve references in help text - Removing serve may break existing MCP client configs — this is intentional (v3 breaking change)
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.
- 2d ago First seen · 107 lines · 0 tokens per session scan A ccea9cce39ad
002_agent_cleanup is an agent published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 851 tokens. 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-09-03.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.