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 skills/svnscha/dap-dbgeng/dap-backtest-loopnpx skills add svnscha/dap-dbgeng --skill dap-backtest-loopgit clone --depth 1 https://github.com/svnscha/dap-dbgengWrote 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/svnscha/dap-dbgeng/dap-backtest-loop)<a href="https://agentmods.dev/skills/svnscha/dap-dbgeng/dap-backtest-loop"><img src="https://agentmods.dev/badge/skills/svnscha/dap-dbgeng/dap-backtest-loop.svg" alt="Measured on agentmods" 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 | $0.00062 | $0.00966 |
| Opus 5 | $0.00031 | $0.00483 |
| Sonnet 5 | $0.00012 | $0.00193 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
dap-backtest-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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Back-testing features against real targets
The loop is: script a scenario -> run it -> read the trace -> fix what it exposes -> keep the trace as a fixture. A feature is back-tested when a recorded session proves it works against a real target and a replay test locks that behavior in.
The harness is C:\Users\svnscha\Code\dap-dbgeng-rc (uv run dap-dbgeng-rc run <scenario>). Scenarios live in src/dapdbgeng_rc/scenarios/.
What can and cannot run in parallel
Live scenarios cannot run in parallel, and no amount of fanning out changes it:
- one desktop: two windows fight over focus, and the Remote Control extension binds one port,
- one kernel target: KDNET accepts a single debugger,
- one service per machine: starting it twice is the same service.
Run live scenarios one at a time. What does parallelize is everything after the trace exists: reading traces, cross-checking the request matrix, drafting fixtures and tests. Fan out there.
Running a scenario
The launch configuration must set trace (a path under recordings/), or the
run produces nothing to analyze:
"trace": "${workspaceFolder}/recordings/kernel.session.json"
The trace is written when the adapter exits cleanly, from the recorder's destructor. A killed adapter leaves no trace - which is itself a finding, not a harness glitch. Copy the file to a scenario-specific name straight after the run; the next run overwrites it.
Reading the trace, not the screen
A scenario that sleeps through a failed session looks exactly like one that worked: steps print, the window looks plausible, nothing fails. Judge a run by its trace, never by the step log.
pwsh scripts/Format-DapSessionFlow.ps1 -Path recordings/<scenario>.session.json
Check: every request the scenario is about is present and status=ok; the stops
match what the scenario asked for; the session ends with exited/terminated
and a disconnect response. Screenshots are for what the viewer sees; the
trace is for what the adapter did. Both lie in different directions, so use
each for its own question.
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.
- 5d ago First seen · 96 lines · 62 tokens per session scan A 579ff49a93f3
dap-backtest-loop is a skill published in the GitHub repository svnscha/dap-dbgeng (10 stars, last pushed 4d ago), licensed MIT. It adds 62 tokens to every session and 966 once invoked, about $0.0003 per session on Opus 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-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
run-integration-tests
Build, pack, and run .NET MAUI integration tests locally. Validates templates, samples, and end-to-end scenarios using the local workload.
cli-e2e-testcase-writer
Use when adding or updating Go CLI E2E coverage for one tests/clie2e/{domain} domain of the compiled lark-cli, especially when the work requires live --help or schema exploration, scenario-based clie2e.RunCmd workflows, and per-domain coverage.md maintenance.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
harness-test-writer
Add regression test cases to the Bifrost provider harness (the Postman collection run via make run-provider-harness-test) based on a merged PR or a GitHub issue. Fetches the PR/issue, traces the affected wire path in the codebase, checks existing harness coverage, designs cases following harness conventions, inserts…
agent-device-evidence
Records iOS/Android native MP4 evidence for test/repro flows extracted from an Expensify GitHub PR or issue. Use when the user asks to "record the flow for PR.