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 RealDougEubanks/ClaudeMarketplace --skill abd-testgit clone --depth 1 https://github.com/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/abd-test)<a href="https://agentmods.dev/skills/realdougeubanks/claudemarketplace/abd-test"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/abd-test/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/realdougeubanks/claudemarketplace/abd-test"><img src="https://agentmods.dev/badge/skills/realdougeubanks/claudemarketplace/abd-test.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.00031 | $0.00388 |
| Opus 5 | $0.00015 | $0.00194 |
| Sonnet 5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
abd-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 9d 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.
What it actually says
ABD — Testing
Adopt the Testing role in the Agent-Based Development workflow.
Read the shared references before acting: envelope and artifact rules, Git rules, MVP gate.
If handoffs/ does not exist, stop and tell the user to run the Planning skill (abd-plan) first — see project-start.md.
Instructions:
- Use Read to read the latest plan artifact from
handoffs/plans/and dev artifacts fromhandoffs/dev/. - Auto-detect the test framework: look for Jest or Vitest by checking
package.json; pytest by checkingpyproject.tomlorsetup.py; Go test by checkinggo.mod; PHPUnit by checkingcomposer.json. - Use Glob with patterns
**/*.test.*,**/*_test.*, andtests/**/*to read existing tests and match their style and patterns. - Write tests covering: happy path, edge cases, invalid input, error conditions, and all acceptance criteria listed in the plan artifact.
- Use Bash to run the test suite and fix any failures before writing the artifact.
- Use Write to create a test artifact at
handoffs/dev/{taskId}_testing_{unixTimestamp}.jsoncontaining status and a test summary (framework detected, number of tests added, pass/fail counts, and any failures resolved).
Follow the output format in envelope.md when reporting.
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.
- 9d ago First seen · 25 lines · 31 tokens per session scan A 7dfb0b8d3314
abd-test is a skill published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 388 once invoked, about $0.0002 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
generate-tasks
Phase 3 of 5 — slices the ARCH doc into verification-ready task specs (tdd/test-after/ui/checklist), emitted as a separate TASKS- - .md file alongside ARCH for the implement skill. Use only when the user asks to run Phase 3 or generate tasks from an ARCH doc — never trigger automatically.
unity-testing
Unity 6 testing guide. Use when writing unit tests, integration tests, or doing TDD with Unity Test Framework. Covers Edit Mode and Play Mode tests, NUnit attributes ([Test], [UnityTest], [SetUp], [TearDown]), testing MonoBehaviours and coroutines, and CI/CD integration. Based on Unity 6.3 LTS documentation.
uw-code-review
Pre-commit code quality review for Unity C# code. Checks against Rules, CODINGSTANDARDS.md, NAMINGCONVENTIONS.md, and GDD Gherkin test coverage. Use when code has been written and tests are passing but before committing. Runs automatically at Step 8.5 of /uw-cmd-implement-feature. Triggers on "review this code"…
feature-dev
Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an…
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
tools-unity-test-framework
Unity Test Framework patterns for EditMode and PlayMode tests including async testing, mocking, and test organization.