What is aid-create-testing-strategy?

A workflow that turns a prepared testing-strategy document into project quality documents covering test levels, expected coverage, CI checks, known gaps, and merge rules.

Use it after preparing a testing-strategy seed to document the test landscape, map tests to continuous-integration checks, define quality thresholds, and set waiver rules.

It helps make testing expectations explicit, including what prevents a change from being merged and who can approve an exception.

How AndreVianna/aid-methodology configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AndreVianna/aid-methodology. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AndreVianna/aid-methodology/master/.claude/skills/aid-create-testing-strategy/SKILL.md

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-create-testing-strategy/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-testing-strategy)

Your own site

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

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

When invoked 2,172 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.00211	$0.02172
Opus 5	$0.00105	$0.01086
Sonnet 5	$0.00042	$0.00434
Haiku 4.5	$0.00021	$0.00217

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

Security

Grade A, and why

aid-create-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 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.

.claude/skills/aid-create-testing-strategy/SKILL.md · 186 lines

How it starts

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

Create Testing Strategy (realize a seed into the C6 documents)

Bind VERB=create, ARTIFACT=testing-strategy -- the create 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. It consumes the seed /aid-design-testing-strategy produces and touches .aid/design/ for no other purpose.

Boundary vs /aid-update-testing-strategy: that skill revises C6 content this lifecycle already committed; this one realizes a seed.
Boundary vs /aid-create-test and /aid-update-test: those author test code; this one writes the strategy and the gate policy.
Not a numbered pipeline phase; does not route to /aid-execute.

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

State: INTAKE

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-create-testing-strategy. phase is not driven.
Read the seed at .aid/design/testing-strategy.md.
Resolve the destinations by concern, not filename. This skill binds concern C6 (quality & testing, .claude/aid/templates/kb-authoring/concern-model.md) and owns two documents. The seed's ## Destination names both halves; where it does not, resolve C6 against .aid/settings.yml knowledge.doc_set, falling back to the C6 row of .claude/aid/templates/kb-authoring/domain-doc-matrix.md, and confirm with the user. An ambiguous realization is asked, never picked silently.
Read both destinations whole where they exist, and note each one's source: field.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: CREATE.

Read the full file on GitHub · 186 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.

10d ago First seen · 186 lines · 211 tokens per session scan A 02c8a5e4b904

Subscribe to this mod's changes

aid-create-testing-strategy is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed today), licensed MIT. It adds 211 tokens to every session and 2,172 once invoked, about $0.0011 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-methodology: Skill for Claude Code