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/juanmhidalgo/claude-plugins/mark-fixedgit clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/juanmhidalgo/claude-plugins/mark-fixed)<a href="https://agentmods.dev/commands/juanmhidalgo/claude-plugins/mark-fixed"><img src="https://agentmods.dev/badge/commands/juanmhidalgo/claude-plugins/mark-fixed.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.00035 | $0.00847 |
| Opus 5 | $0.00017 | $0.00424 |
| Sonnet 5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
mark-fixed 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Branch: !
git branch --show-current - Date: !
date +%Y-%m-%d - Fixes file: REVIEW_FIXES.md (or find the file with
type: review-fixesfrontmatter)
Instructions
Step 1: Load Fixes File
Read the review fixes file found above. If not found, inform user.
Step 2: Determine Mode
Based on $ARGUMENTS:
- Number (e.g., "3") → Verify and mark specific issue #3
- "all" → Verify all pending issues
- Empty → Show pending issues and ask which to verify
Step 3: For Each Issue to Verify
-
Read the issue details:
- File path and line numbers
- Problem description
- Expected solution
-
Verify the fix:
- Read the current file at specified path
- Check if the suggested solution (or equivalent) was implemented
- Look for the problem pattern - should NOT exist anymore
- Look for the fix pattern - should exist now
-
Determine status:
- FIXED - Solution implemented, problem resolved
- PARTIALLY FIXED - Some changes made, but incomplete
- NOT FIXED - Problem still exists
- CANNOT VERIFY - File changed significantly, manual review needed
Step 4: Update the File
For each verified fix:
-
Update checkbox:
- [x] **Completed** -
Add verification note:
**Notes:** - ✅ Verified fixed on YYYY-MM-DD -
Update Progress Summary table:
- Increment "Completed" count
- Decrement "Remaining" count
-
Update frontmatter:
updated: YYYY-MM-DD -
Add to Implementation Log:
| YYYY-MM-DD | 3 | Fixed | @claude | Verified: bulk_create implemented |
Step 5: Report
Show summary:
## Verification Results
✅ Issue #3: N+1 Query - FIXED
✅ Issue #5: Missing validation - FIXED
⚠️ Issue #7: Race condition - PARTIALLY FIXED (missing transaction)
❌ Issue #2: Data migration - NOT FIXED
Progress: 5/11 completed (was 3/11)
Verification Patterns
For code fixes:
# Check if old pattern exists (should NOT)
grep -n "old_pattern" path/to/file.py
# Check if new pattern exists (should)
grep -n "new_pattern" path/to/file.py
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 · 130 lines · 35 tokens per session scan A 4b83d6d6d154
mark-fixed is a command published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 847 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.