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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill debug-test-capturegit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/debug-test-capture)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/debug-test-capture"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/debug-test-capture/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/debug-test-capture"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/debug-test-capture.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.00116 | $0.01530 |
| Opus 5.5 | $0.00046 | $0.00612 |
| Sonnet 5.5 | $0.00023 | $0.00306 |
| Haiku 4.5 | $0.00012 | $0.00153 |
Grade A, and why
debug-test-capture 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 10d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug to Test Capture
Every completed debug session contains exactly the information needed to write a good test: a reproduction case, a root cause, and a verified fix. This skill turns that into a permanent regression guard before the debug context evaporates. A bug that was worth debugging will recur without a test, because nothing else remembers why the code looks the way it does.
When This Runs
After a debug session completes, specifically when:
- A post-fix regression trace returns a clean verdict
- Your debug workflow's final verification gate passes
- A debug workflow marks an issue resolved
- Any bug fix is committed
If you just finished debugging and haven't run this, the debug session is not complete.
Step 1: Extract the test signal from the debug session
Read back through the debug work and pull out:
- The trigger: what user action or system state caused the bug? This becomes the arrange phase.
- The root cause: what was actually wrong? This tells you what the test should assert against.
- The divergence point: where did actual behavior differ from expected? This becomes the assertion.
- The fix: what changed? This tells you what condition the test should verify holds.
- The blast radius: from the regression trace, which adjacent paths were checked? Any without existing tests are candidates.
Step 2: Decide test type and location
Put the test next to the existing tests for that module, and follow the project's naming and layout conventions. If a test file for the module already exists, add to it. If not, create one that matches the neighbors. Look at two or three nearby test files first so the new one reads like it belongs.
Test framework
Use the project's current framework. The shape below is Swift Testing; XCTest and other frameworks map the same way (suite maps to test class or describe block, @Test to a test method, #expect to an assertion).
import Testing
@testable import MyApp
@Suite("Description of what's being tested")
struct FeatureTests {
@Test("Bug description - regression test for [root cause]")
func specificBehavior() async throws {
// arrange: reproduce the conditions that triggered the bug
// act: perform the operation that was broken
// assert: verify the fix holds
}
}
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.
- 10d ago First seen · 155 lines · 116 tokens per session scan A ba60e5abe4b1
debug-test-capture is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 1,530 once invoked, about $0.0005 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-15.
Other skills, from other repositories
run-checks
Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests"…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
debug-failing-test
Debug a failing test using an iterative logging approach, then clean up and document the learning.
agent-qa-result-triage
Triage failed Agent QA runs with MCP evidence, artifacts, logs, fixed failure categories, confidence, and actionable next steps.
health
Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.