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/limps-plan-operationsnpx skills add paulbreuler/limps --skill limps-plan-operationsgit 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/limps-plan-operations)<a href="https://agentmods.dev/skills/paulbreuler/limps/limps-plan-operations"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/limps-plan-operations.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.00037 | $0.03726 |
| Opus 5 | $0.00018 | $0.01863 |
| Sonnet 5 | $0.00007 | $0.00745 |
| Haiku 4.5 | $0.00004 | $0.00373 |
Grade A, and why
limps-plan-operations 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 5d 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Limps Plan Operations
Purpose
Provide reusable patterns for working with limps feature plans across commands. Handles plan identification, path resolution, loading plan artifacts, and shared distillation/lifecycle guidance for planning and agent execution.
LLM Execution Rules
- Use limps MCP tools for all reads/writes when available; do not edit plan files directly.
- Do not include secrets, tokens, or credentials in plan content.
- Only run
process_doc/process_docswith code you authored or reviewed.
Scope
- identify-plan: Resolve a plan name or path to a canonical plan directory name and base path
- load-artifacts: Load all plan artifacts (plan file, interfaces.md, README.md, gotchas.md, agent files) using limps MCP tools
- resolve-path: Convert plan name/path input to canonical
plans/NNNN-descriptive-name/format - distill-agent-files: Apply distillation rules and size guidance for
*.agent.mdgeneration - lifecycle: Provide standard lifecycle and command usage context
MCP Tool Usage
All operations use limps MCP tools with server "limps":
Document & Plan Tools
list_plans- List available planslist_agents- List agents for a planprocess_doc- Read and analyze a single documentprocess_docs- Read and analyze multiple documents (e.g., all agent files)create_plan- Create a new plan structurecreate_doc- Create a new documentupdate_doc- Update an existing documentsearch_docs- Full-text search across documents
Health & Integrity Tools
check_staleness- Report stale plans/agents based on modification timecheck_drift- Verify agent file references match actual filesysteminfer_status- Suggest status updates based on dependency completion
Proposals & Scoring Tools
get_proposals- List update proposals from staleness, drift, and inferenceapply_proposal- Apply a single proposal with confirmationconfigure_scoring- Update scoring weights, presets, and biases
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.
- 5d ago First seen · 461 lines · 37 tokens per session scan A 8a642b951d73
limps-plan-operations is a skill published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It adds 37 tokens to every session and 3,726 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, 活期年化高了通知我, 监控活期.