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 AndreVianna/aid-methodology --skill aid-update-testing-strategygit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-update-testing-strategy)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-testing-strategy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-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.
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-testing-strategy"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-testing-strategy.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.00183 | $0.01665 |
| Opus 5 | $0.00092 | $0.00833 |
| Sonnet 5 | $0.00037 | $0.00333 |
| Haiku 4.5 | $0.00018 | $0.00167 |
Grade A, and why
aid-update-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 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Testing Strategy (revise the C6 documents)
Bind VERB=update, ARTIFACT=testing-strategy -- the update 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.
- Boundary vs
/aid-create-testing-strategy: that skill realizes a seed and owns the creation path; this one is the maintenance verb. Where a destination is absent this skill routes there rather than standing one up itself. - Boundary vs
/aid-create-testand/aid-update-test: those author test code; this one revises the strategy and the gate policy. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> UPDATE -> VERIFY -> PRESENT -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry
line on each state.
State: INTAKE
- Require a stated change. Empty argument -> ask one bootstrapping question ("What should change in the testing strategy or the gate policy?") and wait.
- Allocate through the Work Initiation Gate exactly as the contract's Allocation rule
requires (
.claude/skills/aid-design/SKILL.mdINTAKE step 4 is the shape), withinitiator: aid-update-testing-strategy.phaseis not driven. - No seed is required. The change stated in this run is a sufficient input, and this
skill completes without a seed. Read and consume one when present at
.aid/design/testing-strategy.md, carrying its## Current directioninto the destinations and deleting it once realized. - Resolve the destinations by concern. This skill binds concern C6 (quality &
testing) and owns two documents. Where a seed supplied a
## Destination, use it; otherwise apply the concern rule here -- resolve C6 against.aid/settings.ymlknowledge.doc_set, falling back to the C6 row of.claude/aid/templates/kb-authoring/domain-doc-matrix.md-- and confirm the resolution with the user before writing. Never resolve silently. - Read both destinations whole, and note each one's
source:field. An absent destination -> route to/aid-create-testing-strategyfor that document and write nothing there. - Classify complexity for the
aid-architectdispatch (verifier tier >= producer).
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 · 149 lines · 183 tokens per session scan A b4515935fb2b
aid-update-testing-strategy is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 183 tokens to every session and 1,665 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-09-03.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.