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 commands/plipowczan/claude-piv-skeleton/implement-fixgit clone --depth 1 https://github.com/plipowczan/claude-piv-skeletonWrote 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/plipowczan/claude-piv-skeleton/implement-fix)<a href="https://agentmods.dev/commands/plipowczan/claude-piv-skeleton/implement-fix"><img src="https://agentmods.dev/badge/commands/plipowczan/claude-piv-skeleton/implement-fix.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.00006 | $0.01766 |
| Opus 5 | $0.00003 | $0.00883 |
| Sonnet 5 | $0.00001 | $0.00353 |
| Haiku 4.5 | $0.00001 | $0.00177 |
Grade A, and why
implement-fix 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 — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Fix: Execute RCA Solution
RCA Document
Read RCA document: $ARGUMENTS
Example: .claude/agents/reviews/rca-123-bug-title.md
Purpose
Implement a bug fix based on a comprehensive Root Cause Analysis.
Process: Use systematic approach for bug fixing
Implementation Process
1. Read and Understand RCA
Read the entire RCA document:
- Understand the issue
- Understand the root cause
- Review the fix strategy
- Note the testing strategy
- Note the acceptance criteria
Clarify Ambiguities:
- If RCA is unclear, ask questions
- Get specific implementation details
- Resolve approach decisions
2. Verify Feature Branch
CRITICAL: You MUST be on a feature branch for bug fixes!
Check current branch:
git branch --show-current
If on main branch:
- STOP - Do not implement fixes on main!
- Ask user: "Should I create a feature branch for this bug fix?"
- If approved, create branch:
git checkout -b fix/issue-{number}-{brief-description} - Then proceed with implementation
If on feature branch:
- ✅ Continue with implementation
- Verify branch name follows convention:
fix/issue-{number}-{description}
Rationale:
- Protects main branch from untested fixes
- Allows for review before merging
- Facilitates rollback if fix introduces issues
- Enables testing in isolation
3. Create Mini-Plan
Unlike feature development, bug fixes are simpler. Create a mini-plan:
# Fix Plan: Issue #{number}
## Root Cause
[From RCA]
## Fix Strategy
[From RCA]
## Files to Modify
- `path/to/file1.java` - [What to change]
- `path/to/file2.java` - [What to change]
## Implementation Steps
1. Step 1: [Description]
2. Step 2: [Description]
3. Step 3: [Description]
## Testing Strategy
[From RCA]
## Validation
[From RCA]
Save to: .claude/agents/plans/fix-issue-{number}.md
4. Read Context
Read necessary context:
- Read files to be modified
- Understand current implementation
- Identify patterns to follow
- Note related code that might be affected
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 · 333 lines · 6 tokens per session scan A f5fc1aa10c44
implement-fix is a command published in the GitHub repository plipowczan/claude-piv-skeleton (4 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 1,766 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.