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 skills add paulbreuler/limps --skill limps-planninggit 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-planning)<a href="https://agentmods.dev/skills/paulbreuler/limps/limps-planning"><img src="https://agentmods.dev/badge/skills/paulbreuler/limps/limps-planning.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.00025 | $0.00455 |
| Opus 5 | $0.00013 | $0.00228 |
| Sonnet 5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
limps-planning 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.
What it actually says
limps planning
Purpose
Provide consistent guidance for selecting limps MCP tools in common planning workflows.
When to Use
- Creating or updating plans and agents
- Finding the next task or plan status
- Searching or updating documents in a plans directory
Quick Tool Selection
- Create a plan:
create_plan, thencreate_docfor plan files - List plans:
list_plans - List agents:
list_agents - Plan status:
get_plan_status - Next task:
get_next_task - Search docs:
search_docs - Update status:
update_task_status - Read/process docs:
process_doc,process_docs - Update plan priority/severity:
update_doc(edit plan frontmatter)
Examples
Find the next task in a plan
list_plans→ pick plan nameget_next_taskwith plan number/name
Update an agent status
list_agentsfor the planupdate_task_statuswith task ID and new status
Automate plan priority and severity
process_docthe plan file (e.g.,plans/0030-foo/0030-foo-plan.md) to read frontmatter- Determine
priorityandseverityvalues (low | medium | high | critical) update_docwith new frontmatter fields (do not edit config.json)- Optional: add a brief note in plan content or decisions log describing why it was updated
Extract open features across plans
process_docswith patternplans/*/*-plan.md- Use
extractFeatures()to filterGAP
Notes
- Paths should be relative to the configured
plansPathordocsPaths. - Use
process_doc(s)for structured extraction instead of manual parsing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 58 lines · 25 tokens per session scan A feecea27c5ea
limps-planning is a skill published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 455 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
knowledge-layered-configuration-and-runtime-settings
A configuration system that combines user, project, local, and per-call settings, then saves each field to the correct scope and file. It can rebuild settings for a particular source project.
linearis
Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user mentions Linear, a ticket identifier like…
knowledge-agent-execution-and-orchestration-goals-tasks-and-scheduling
A system for persistent goals, task lists, independent task sessions, isolated worktrees, and cron, interval, or one-time schedules.
github
GitHub CLI (gh) for repository management, issues, pull requests, releases, workflows, search, gists, and API access. Use when the user asks about any GitHub operation — creating repos, forking, cloning, PR workflows, issue triage, CI/CD runs, code search, release management, or direct API calls. Keywords: github, gh…
knowledge-agent-execution-and-orchestration-agent-teams
A coordination system for teams of coding agents, with shared tasks, dependencies, messages, member status, and access checks.
knowledge-session-state-and-context
A codebase guide for storing agent sessions, rebuilding their visible state, recovering active work, branching or rewinding history, and shortening context sent to the model.