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 proffesor-for-testing/agentic-qe --skill debug-loopgit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/debug-loop)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/debug-loop"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/debug-loop/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/proffesor-for-testing/agentic-qe/debug-loop"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/debug-loop.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.00027 | $0.00498 |
| Opus 5.5 | $0.00011 | $0.00199 |
| Sonnet 5.5 | $0.00005 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
debug-loop 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debug-loop — 95% identical, 2 lines differ
What it actually says
Debug Loop
Autonomous hypothesis-driven debugging against real data. No guessing, no simulating.
Arguments
<symptom>— Description of the bug or unexpected behavior. If omitted, prompt the user.
Phases
Phase 1 — Reproduce
Run the exact command that shows the bug. Capture and display the REAL output. Confirm the bug is visible.
If the bug cannot be reproduced, stop and explain what was tried.
Phase 2 — Hypothesize and Test (up to 5 iterations)
For each iteration:
- State a specific hypothesis (e.g., "the query targets v2 tables but data is in v3 tables")
- Run a REAL command to test it (e.g.,
sqlite3 [db path] '.tables'thenSELECT COUNT(*) FROM [table]) - Record whether the hypothesis was confirmed or rejected
- If rejected, form the next hypothesis based on what you learned
Do NOT make code changes until you have a confirmed root cause.
Important checks:
- Always check both v2 and v3 SQLite tables when data issues are suspected
- Check dependency versions (e.g., sqlite3 vs better-sqlite3)
- Check for hardcoded values that may have been missed
Phase 3 — Fix
Make the minimal targeted fix. Explain:
- What the root cause was
- What you're changing and why
- What the blast radius is (which other code paths are affected)
Before applying, grep for ALL instances of the problematic pattern across the entire codebase.
Phase 4 — Verify
Run the SAME reproduction command from Phase 1. The output must now show correct values. If it doesn't, go back to Phase 2.
Show before/after output comparison.
Phase 5 — Regression
npm test
Run the full test suite. If tests fail, fix them before committing.
Rules
- NEVER guess or simulate output — always run real commands
- NEVER make code changes before confirming root cause
- Always check for the pattern across the entire codebase, not just one file
- If blocked after 5 hypotheses, stop and ask the user for guidance
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.
- 8d ago First seen · 62 lines · 27 tokens per session scan A f87077dace5b
debug-loop is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (505 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 498 once invoked, about $0.0001 per session on Opus 5.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-10-11.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…