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 skills/avibebuilder/claude-prime/fixnpx skills add avibebuilder/claude-prime --skill fixgit clone --depth 1 https://github.com/avibebuilder/claude-primeWhat 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.00148 | $0.00841 |
| Opus 5 | $0.00074 | $0.00420 |
| Sonnet 5 | $0.00030 | $0.00168 |
| Haiku 4.5 | $0.00015 | $0.00084 |
Grade A, and why
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 3d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think harder. Remove the cause with the change that genuinely restores the intended behavior. Making the symptom disappear without explaining the evidence is not a fix.
Process
Check conversation context and skip completed steps.
1. Read the bug, then choose the lane
Read the symptom, expected behavior, errors, logs, failing tests, and any prior diagnosis. Separate confirmed facts from guesses. Then route:
| Situation | Action |
|---|---|
| Clear root cause or one strongly evidenced failing area | Stay in /fix |
| One narrow check would remove the last uncertainty | Do that check inside /fix, then commit to a lane |
| Multiple plausible causes, unclear failing area, or needs runtime instrumentation | Switch to /diagnose first |
| Bug is understood but multiple defensible fixes with real tradeoffs | Switch to /discuss |
If you're about to add a speculative guard or workaround because the cause is still fuzzy, you're in the wrong lane. If evidence is insufficient, switch to /diagnose instead of guessing.
GATE: If a plan was requested or produced, wait for user approval before implementation.
1.5 Reboot after repeated misses
After 3 substantive fix attempts that haven't resolved the bug, stop thrashing. Write a handoff note covering: bug context, confirmed evidence, files checked, each failed approach and why it failed, open questions, and most likely next diagnostic branch. Start a fresh Claude session with the handoff note (or give it to the user to paste). Repeated failures signal contaminated context or narrowed reasoning — a clean window gets fresh judgment. Let stop and enjoy the world, you just did the best thing bro!
2. Repair the cause
- Apply the smallest change that removes the root cause
- Correct the bad state transition, condition, query, or data flow rather than masking the symptom at the crash site
- Call-stack upstream rule: when a function crashes on bad data (
undefined,null, wrong type), trace back to where that data was produced or passed. Fix the producer or caller, not the victim. Example:applyDiscount(cart, coupon)crashes becausecouponisundefined→ fix the lookup or call site that passed bad data, notapplyDiscount - Follow existing code patterns and keep scope tight
- Keep temporary instrumentation that helps prove the repair until verification is complete, then remove it
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.
- 3d ago First seen · 58 lines · 148 tokens per session scan A dd3ac130b4a6
fix is a skill published in the GitHub repository avibebuilder/claude-prime (119 stars, last pushed 3mo ago), licensed MIT. It adds 148 tokens to every session and 841 once invoked, about $0.0007 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-30.
Other skills, from other repositories
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
research-report
Summarize deep research results into markdown report, cover all fields, skip uncertain values.
ln-21-documentation-auditor
Audits documentation and code comments for structure, coverage, factual accuracy, and maintainability. Use for documentation trust reviews; not code, test, or architecture audits.
ln-41-test-strategy-planner
Designs risk-based test portfolio decisions and prioritized scenarios without changing code. Use when requirements need a test strategy; not for auditing or implementing tests.