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 qaml-ai/camelAI --skill testing-debugginggit clone --depth 1 https://github.com/qaml-ai/camelAIWrote 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/qaml-ai/camelai/testing-debugging)<a href="https://agentmods.dev/skills/qaml-ai/camelai/testing-debugging"><img src="https://agentmods.dev/badge/skills/qaml-ai/camelai/testing-debugging/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/qaml-ai/camelai/testing-debugging"><img src="https://agentmods.dev/badge/skills/qaml-ai/camelai/testing-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.02428 |
| Opus 5.5 | $0.00019 | $0.00971 |
| Sonnet 5.5 | $0.00010 | $0.00486 |
| Haiku 4.5 | $0.00005 | $0.00243 |
Grade A, and why
testing-debugging 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 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.
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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing and Debugging
This skill guides debugging deployed applications and writing tests for rapid iteration. The key insight: unit tests are the fastest way to reproduce and fix bugs.
The Unit Test Debugging Workflow
This is the most effective debugging workflow. Instead of repeatedly deploying and manually testing in the browser, write a unit test that reproduces the bug:
Why Unit Tests for Debugging?
| Approach | Cycle Time | Reliability |
|---|---|---|
| Deploy → Browser → Manual test | 30-60 seconds | Variable |
| Run unit test | 1-2 seconds | Consistent |
A 30x speedup means you can iterate 30 times faster. This compounds: what takes an hour with manual testing takes 2 minutes with unit tests.
The Workflow
-
Understand the bug - Read the user report, check console errors, understand expected vs actual behavior
-
Write a failing test - Create a test that reproduces the exact failure
// Example: User reports "discount not applied to cart total" test('applies discount code to cart total', () => { const cart = createCart([ { name: 'Widget', price: 100 }, { name: 'Gadget', price: 50 } ]); cart.applyDiscount('SAVE20'); // 20% off expect(cart.total).toBe(120); // Was returning 150 }); -
Run the test to confirm it fails - Verify you've reproduced the bug
bun test -
Fix the code - Make changes to fix the failing test
-
Run the test again - Confirm the fix works
bun test -
Deploy - Once tests pass, publish through the mediated project tool (not a package-manager or Wrangler deploy command)
await tools.deploy_project({ project: "<project-name>" });
Test File Location
Place test files next to the code they test:
src/
cart.ts
cart.test.ts # Tests for cart.ts
utils/
discount.ts
discount.test.ts
Or use a __tests__ directory:
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 · 332 lines · 48 tokens per session scan A a49905367353
testing-debugging is a skill published in the GitHub repository qaml-ai/camelAI (390 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,428 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.