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/dgk-dev/dgk-gpt/testnpx skills add dgk-dev/dgk-gpt --skill testgit clone --depth 1 https://github.com/dgk-dev/dgk-gptWrote 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/dgk-dev/dgk-gpt/test)<a href="https://agentmods.dev/skills/dgk-dev/dgk-gpt/test"><img src="https://agentmods.dev/badge/skills/dgk-dev/dgk-gpt/test.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.00074 | $0.00868 |
| Opus 5 | $0.00037 | $0.00434 |
| Sonnet 5 | $0.00015 | $0.00174 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
test 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test
Use this as a verification-and-fix mode after implementation or during bug hunts. This is not just "run one test command". It is a persistent loop that keeps narrowing failures and rerunning checks until the requested behavior is verified.
Default Loop
- Define the verification target.
- affected files, routes, surfaces, and user-visible claims
- exact stopping condition for signoff
- Build the smallest credible test matrix from the repo and task.
- code-level checks first
- integration and e2e next
- live runtime QA last
- Run the relevant existing automated checks before inventing custom ones.
- prefer repo-native scripts and targeted specs or files
- use the stack already present: Vitest, Jest, Playwright, Cypress, pytest, go test, etc.
- widen scope only after the narrow failing checks pass
- If the surface is interactive, verify the real runtime too.
- web: run relevant e2e flows or drive the app directly
- before browser DevTools inspection, probe
http://127.0.0.1:9333/json/version - if it is already live, reuse it
- if it is not live and a
chromelauncher exists, start it automatically, wait for the port, then usechrome-devtools - browser diagnosis: use
chrome-devtoolsfor console, network, DOM, accessibility, or performance inspection - before Pix desktop DevTools inspection, probe
http://127.0.0.1:9334/json/version - if it is already live, reuse it
- if it is not live and a
tauri-pixlauncher exists, start it automatically, wait for the port, then usetauri-devtools - Tauri desktop: use
tauri-devtoolsand the fixed Tauri debug path when diagnosis is needed - direct browser control: use the repo's Playwright setup or a persistent
js_replPlaywright session when targeted manual proof is still needed
- On failure, fix and rerun.
- repeat inspect -> patch -> rerun narrow checks -> rerun broader confidence checks
- do not stop after the first or second failed attempt
- Before signoff, rerun the checks that support the final claims.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 72 lines · 74 tokens per session scan A 10e22519d212
test is a skill published in the GitHub repository dgk-dev/dgk-gpt (53 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 868 once invoked, about $0.0004 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-30.
Other skills, from other repositories
codex-delegate
Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" …
commandcode-delegate
Delegate a coding task to the Command Code CLI (cmd) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Command Code — phrasings like "have Command Code do X", "delegate this to commandcode", "run it through cmd", or "use Command Code…
warp-delegate
Delegate a coding task to the Warp Agent CLI (oz) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Warp - phrasings like "have Warp implement X", "delegate this to the Warp CLI", "run it through Warp", "use oz to…
agy-delegate
Delegate a coding task to the Google Antigravity CLI (agy) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Antigravity or agy - phrasings like "have Antigravity do X", "delegate this to agy", "run it through agy", or "use…
claude-delegate
Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement…
cursor-delegate
Delegate a coding task to the Cursor Agent CLI (cursor-agent) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Cursor — phrasings like "have Cursor implement X", "delegate this to Cursor", "run it through Cursor Agent", or "use…