What is aid-design-testing-strategy?

A planning aid for deciding how a project should be tested. It records test levels, expected coverage, merge-blocking checks, and who can approve exceptions.

Use it to define the project's testing approach before creating the actual testing-policy documents or test cases.

It separates testing policy decisions from writing or running individual tests, so the team can agree on rules before implementation.

aid-design-testing-strategy — Skill for Claude Code by AndreVianna

Install

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.

Any agent

npx skills add AndreVianna/aid-methodology --skill aid-design-testing-strategy

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-testing-strategy/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-testing-strategy)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-testing-strategy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-testing-strategy/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-testing-strategy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-design-testing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 172 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,225 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00172	$0.01225
Opus 5	$0.00086	$0.00613
Sonnet 5	$0.00034	$0.00245
Haiku 4.5	$0.00017	$0.00122

Measured 12d ago against content hash f0c9b301d195, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

aid-design-testing-strategy 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 12d 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.

.claude/skills/aid-design-testing-strategy/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Design Testing Strategy (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=testing-strategy -- the design stage in the contract's vocabulary -- then follow the shared contract at .claude/aid/templates/design-lifecycle.md. This skill binds that contract and restates none of its rules. The seed it writes is .aid/design/testing-strategy.md; realizing it into the project's C6 document(s) is /aid-create-testing-strategy's job, not this one's.

Boundary vs /aid-create-testing-strategy: that skill realizes the seed into the C6 document(s); this one only develops the seed. Neither resolves anything on its own.
Boundary vs /aid-design-test and /aid-test: /aid-design-test designs specific tests, not the policy; /aid-test runs existing suites rather than designing them.
Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> DESIGN -> VERIFY (loop) -> PRESENT [user decides] -> DONE, as design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

Require a subject. Empty argument -> ask one bootstrapping question ("What testing policy do you want to design -- its levels, coverage expectations, and merge-blocking gates?") and wait.
Allocate through the Work Initiation Gate exactly as the contract's Allocation rule requires (.claude/skills/aid-design/SKILL.md INTAKE step 4 is the shape), with initiator: aid-design-testing-strategy. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/testing-strategy.md if a prior seed exists -- re-invocation iterates it rather than starting over.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: DESIGN.

State: DESIGN

Dispatch aid-architect (clean context, tiered) to write or iterate .aid/design/testing-strategy.md in the seed shape the contract fixes (design-seed.md; feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read in INTAKE. What this artifact's seed must settle: the test levels, coverage expectations, which gates block a merge, and who may waive one.

Read the full file on GitHub · 104 lines

Changes

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.

12d ago First seen · 104 lines · 172 tokens per session scan A f0c9b301d195

Subscribe to this mod's changes

aid-design-testing-strategy is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 172 tokens to every session and 1,225 once invoked, about $0.0009 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

aid-design-testing-strategy