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 skills add GuitarAlchemist/ga --skill devfixgit clone --depth 1 https://github.com/GuitarAlchemist/gaWrote 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/skills/guitaralchemist/ga/devfix)<a href="https://agentmods.dev/skills/guitaralchemist/ga/devfix"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/devfix/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/skills/guitaralchemist/ga/devfix"><img src="https://agentmods.dev/badge/skills/guitaralchemist/ga/devfix.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.00621 |
| Opus 5.5 | $0.00000 | $0.00248 |
| Sonnet 5.5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
devfix scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:5176 -o /dev/null -w "%{http_code}" 2>&1 # Vite How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/devfix — Emergency Dev Stack Recovery
When to use
- Site shows 502 Bad Gateway on demos.guitaralchemist.com
- Vite dev server is down (port 5176 not responding)
- API server is down or unhealthy (port 5232)
- User says "site is down", "502", "cloudflare error", "can't access demos"
What it does
Diagnoses and fixes the dev stack in 30 seconds:
Step 1: Diagnose
# Check what's running
curl -s http://localhost:5176 -o /dev/null -w "%{http_code}" 2>&1 # Vite
curl -s http://localhost:5232/health 2>&1 # API
curl -s -o /dev/null -w "%{http_code}" https://demos.guitaralchemist.com 2>&1 # Tunnel
Step 2: Report
Tell the user exactly what's wrong:
- Vite down (port 5176) → 502 on demos site. Most common issue.
- API down (port 5232) → API calls fail, but static site may work.
- Both down → Full outage.
- Tunnel down (cloudflared not running) → Rare. Check
Get-Process cloudflared.
Step 3: Fix
Tell the user to run ONE of these:
Quick fix (Vite only):
! cd ReactComponents/ga-react-components && npx vite --host --port 5176
Full fix (Vite + API):
! pwsh Scripts/start-dev.ps1
Nuclear option (everything including Aspire):
! pwsh Scripts/start-all.ps1 -NoBuild -Dashboard
Step 4: Verify
# Wait 10s then check
curl -s -o /dev/null -w "%{http_code}" https://demos.guitaralchemist.com
Architecture
- Cloudflare Tunnel (cloudflared) → routes demos.guitaralchemist.com to localhost:5176
- Vite (port 5176) → serves React frontend, proxies /api/* to localhost:5232
- GaApi (port 5232) → .NET backend
- Tunnel process usually survives reboots (Windows service), but Vite/API don't auto-restart
Common causes of 502
- Vite crashed or was never started after a reboot
npm run buildkilled the dev server process- Port conflict (another process on 5176)
- Windows update restarted the machine
Do NOT
- Don't restart cloudflared unless the tunnel itself is broken
- Don't run
start-all.ps1with-Dashboardunless Aspire is needed - Don't rebuild — use
-NoBuildflag for speed
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 · 68 lines · 0 tokens per session scan A d60b7a33fa39
devfix is a skill published in the GitHub repository GuitarAlchemist/ga (2 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 621 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.