Borrowing it
Nothing to install: this file belongs to paulbreuler/limps. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/paulbreuler/limps/main/.claude/commands/close-feature-agent.mdgit 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/commands/paulbreuler/limps/close-feature-agent)<a href="https://agentmods.dev/commands/paulbreuler/limps/close-feature-agent"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/close-feature-agent/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.
<a href="https://agentmods.dev/commands/paulbreuler/limps/close-feature-agent"><img src="https://agentmods.dev/badge/commands/paulbreuler/limps/close-feature-agent.svg" alt="Reviewed on agentmods" width="80" 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.01784 |
| Opus 5.5 | $0.00000 | $0.00714 |
| Sonnet 5.5 | $0.00000 | $0.00357 |
| Haiku 4.5 | $0.00000 | $0.00178 |
Grade A, and why
close-feature-agent 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 1mo 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Feature Agent v2.0.0
Verify agent completion, sync status, and identify unblocked work.
Invocation
/close-feature-agent [path-to-agent-file]
Example:
/close-feature-agent plans/0004-feature-name/agents/000_agent_name.agent.md
What This Command Does
- Verify completion - Check agent delivered what was promised
- Sync status - Update README.md status matrix
- Report unblocked - Show what can now proceed
- Capture gotchas - Ensure discoveries are in gotchas.md
What This Command Does NOT Do
- Regenerate other agent files (use
update-feature-plan) - Modify source code
- Merge PRs
- Assign next work
Workflow
Step 1: Parse Agent File
Read the agent's .agent.md using limps MCP process_doc tool and extract:
- Feature IDs and their status
- Exported interfaces claimed
- Files that should exist
- Gotchas section
Step 2: Verify Completion
For each feature marked PASS:
Check files exist:
- [ ] src/components/Column/ColumnHeader.tsx exists
- [ ] src/components/Column/ColumnHeader.test.tsx exists
- [ ] src/components/Column/ColumnHeader.stories.tsx exists
Check exports match interface (spot check):
- [ ] useColumnHeader exports match declared signature
- [ ] ColumnHeader component exports match declared signature
Check tests pass:
- [ ] Run project test suite for affected files
Step 3: Sync Status
Update README.md status matrix using limps MCP update_doc tool:
Before:
| 2 | Headers | Columns | 🔄 WIP | - |
| 3 | Resize | Columns | ❌ GAP | #2 |
After:
| 2 | Headers | Columns | ✅ PASS | - |
| 3 | Resize | Columns | ✅ PASS | - |
Update dependency graph colors if present.
Step 4: Update Task Status
Use limps MCP update_task_status to mark features as PASS. Task status is stored in agent file frontmatter.
Agent-only plans (no feature IDs):
- If the agent file does not list feature IDs (e.g., only agent tasks), skip
update_task_status. - Add a note in the output that task status updates require feature IDs.
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.
- 1mo ago First seen · 288 lines · 0 tokens per session scan A 8b7912f68bff
close-feature-agent is a command published in the GitHub repository paulbreuler/limps (10 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,784 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-08-31.
Other commands, from other repositories
next
Suggest the most likely next workflow action based on current context.
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).
aigon-research-context
Record the original author's durable, transcript-free handoff.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.