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/latestaiagents/agent-skills/debug-thisgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWhat 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.00010 | $0.00824 |
| Opus 5 | $0.00005 | $0.00412 |
| Sonnet 5 | $0.00002 | $0.00165 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
debug-this 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -v https://api.example.com/endpoint How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debug-this
Structured debugging workflow. Describe the bug and I'll help you find and fix it.
Describe the Bug
Tell me:
- What should happen? (expected behavior)
- What actually happens? (actual behavior)
- When did it start? (recent changes?)
- Error messages? (paste any errors)
Debugging Workflow
Step 1: Reproduce the Bug
First, I need to reliably trigger the bug:
## Reproduction Steps
1. [Step to reproduce]
2. [Step to reproduce]
3. [Bug occurs]
**Reproducible:** Always / Sometimes / Rarely
**Environment:** Dev / Staging / Prod
**Affected users:** All / Some / One
Step 2: Form Hypotheses
Based on symptoms, I'll generate hypotheses ranked by likelihood:
## Hypotheses
1. **[Most likely]** Description
- Evidence for: ...
- Evidence against: ...
- How to verify: ...
2. **[Second likely]** Description
- Evidence for: ...
- Evidence against: ...
- How to verify: ...
3. **[Third likely]** Description
- ...
Step 3: Gather Evidence
For each hypothesis, I'll suggest specific checks:
// Add diagnostic logging
console.log('[DEBUG] Variable state:', { var1, var2, var3 });
// Check database state
SELECT * FROM orders WHERE id = 123;
// Verify API responses
curl -v https://api.example.com/endpoint
// Check logs
grep "ERROR\|Exception" /var/log/app.log | tail -50
Step 4: Isolate the Cause
Narrow down using:
| Technique | When to Use |
|---|---|
| Binary search | Bug in large codebase, use git bisect |
| Simplify inputs | Bug depends on specific data |
| Remove components | Bug might be in dependencies |
| Fresh environment | Bug might be env-specific |
Step 5: Fix and Verify
## Fix
**Root cause:** [What was actually wrong]
**Fix:** [Code change]
**Verification:**
- [ ] Bug no longer reproduces
- [ ] Related features still work
- [ ] Tests pass
- [ ] No new errors in logs
Step 6: Prevent Recurrence
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 · 144 lines · 10 tokens per session scan A 26b0a500fefa
debug-this is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 824 once invoked, about $0.0001 per session on Opus 5. 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 commands, from other repositories
fw-setup-use
Workspace FDK stack switch — nvm use from .nvmrc or explicit 10/9 (Node 24.11 vs 18); optional --write-nvmrc and --global flags.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.
fdk-fix
Fix all platform validation errors and lint errors in a Freshworks app. Runs fdk validate, identifies fatal errors and lint issues, applies fixes iteratively, and re-validates until all errors are resolved.
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fw-setup-status
Check FDK and Node.js installation status (/fw-setup status); optional --verbose diagnostics.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.