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/003_agent_close-workflowgit 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/003_agent_close-workflow)<a href="https://agentmods.dev/agents/paulbreuler/limps/003_agent_close-workflow"><img src="https://agentmods.dev/badge/agents/paulbreuler/limps/003_agent_close-workflow.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.00383 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
003_agent_close-workflow 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.
What it actually says
Agent 3: Close Workflow Alignment
Plan Location: plans/0039-llm-usage-improvements/0039-llm-usage-improvements-plan.md
Scope
Features: #4
Own: .claude/commands/close-feature-agent.md, .claude/commands/run-agent.md
Depend on: none
Block: none
Interfaces
Export
// #4
(none)
Receive
// None
Features
#4: Agent Close Workflow Alignment
TL;DR: Align close-feature-agent and run-agent workflows for agent-only plans.
Status: PASS
Test IDs: close-feature-agent skips update_task_status for agent-only plans, close-feature-agent emits note for agent-only status, run-agent validates agent path, run-agent prints checklist
Files: .claude/commands/close-feature-agent.md (modify), .claude/commands/run-agent.md (modify)
TDD:
close-feature-agent skips update_task_status for agent-only plans→ impl → refactorclose-feature-agent emits note for agent-only status→ impl → refactorrun-agent validates agent path→ impl → refactorrun-agent prints checklist→ impl → refactor
Gotchas:
- Preserve existing behavior for plans with real feature IDs.
Done
- TDD cycles pass
- Exports match interface
- Test IDs implemented
- Status → PASS
LIMPS Graph Links
Plan:
Depends on: No dependencies found
Blocks: No blocks found
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 · 69 lines · 0 tokens per session scan A 272c28afd1c9
003_agent_close-workflow 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 383 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.