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 wyattowalsh/agents --skill test-architectgit clone --depth 1 https://github.com/wyattowalsh/agentsWrote 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/wyattowalsh/agents/test-architect)<a href="https://agentmods.dev/skills/wyattowalsh/agents/test-architect"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/test-architect/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/wyattowalsh/agents/test-architect"><img src="https://agentmods.dev/badge/skills/wyattowalsh/agents/test-architect.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.00043 | $0.02413 |
| Opus 5.5 | $0.00017 | $0.00965 |
| Sonnet 5.5 | $0.00009 | $0.00483 |
| Haiku 4.5 | $0.00004 | $0.00241 |
Grade A, and why
test-architect 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 1mo 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect
Design test strategies, analyze coverage gaps, identify edge cases, diagnose flaky tests, and audit test suite architecture.
Scope: Test design and analysis only. NOT for running tests or CI/CD (devops-engineer), code review (review), or TDD workflow.
Dispatch
| $ARGUMENTS | Action |
|---|---|
design <feature/module> |
Design test strategy and pyramid for a feature or module |
generate <file/function> |
Generate test cases (strategy text or actual test code based on context) |
gaps |
Analyze coverage gaps from coverage reports |
edge-cases <function> |
Systematic edge case identification for a function |
flaky |
Diagnose flaky tests from logs and code |
review |
Audit test suite architecture |
| Empty | Show mode menu with examples |
Canonical Vocabulary
Use these terms exactly throughout all modes:
| Term | Definition |
|---|---|
| test pyramid | Layered test distribution: unit (base), integration (middle), e2e (top) |
| coverage gap | Code path with no test coverage, weighted by complexity risk |
| edge case | Input at boundary conditions, null/empty, type coercion, overflow, unicode, concurrent |
| flaky test | Test with non-deterministic pass/fail behavior across identical runs |
| mutation score | Percentage of injected mutations detected by the test suite |
| test strategy | Document defining what to test, how, at what layer, with what tools |
| property-based test | Test asserting invariants over generated inputs (Hypothesis/fast-check) |
| test isolation | Guarantee that tests do not share mutable state or execution order dependencies |
| fixture | Reusable test setup/teardown providing controlled state |
| test surface | Set of public interfaces, code paths, and states requiring test coverage |
Mode 1: Design
/test-architect design <feature/module>
Surface Analysis
- Read the feature/module code. Map the test surface: public API, internal paths, state transitions, error conditions.
- Classify complexity: simple (pure functions), moderate (I/O, state), complex (distributed, concurrent, multi-service).
What ships with it
29 files 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.
- data/edge-case-heuristics.json 2.6 KB
- data/test-framework-patterns.json 3.0 KB
- evals/coverage-gaps.json 561 B
- evals/design-strategy.json 590 B
- evals/edge-cases.json 589 B
- evals/evals.json 2.2 KB
- evals/implicit-trigger.json 759 B
- evals/negative-control.json 521 B
- evals/test-design.json 483 B
- references/coverage-analysis.md 3.0 KB
- references/edge-case-heuristics.md 3.6 KB
- references/flaky-diagnosis.md 3.4 KB
- references/framework-patterns.md 3.6 KB
- references/mutation-testing.md 2.5 KB
- references/property-testing.md 3.0 KB
- references/test-pyramid.md 2.6 KB
- references/test-suite-audit.md 3.9 KB
- scripts/asset_toolkit/__init__.py 303 B runs code
- scripts/asset_toolkit/_shared.py 5.6 KB runs code
- scripts/asset_toolkit/common.py 3.0 KB runs code
- scripts/asset_toolkit/package.py 43 KB runs code
- scripts/asset_toolkit/validate_evals.py 11 KB runs code
- scripts/asset_toolkit/validate_hooks.py 13 KB runs code
- scripts/asset_toolkit/validate_skill.py 3.6 KB runs code
- scripts/check.py 2.2 KB runs code
- scripts/coverage-analyzer.py 4.5 KB runs code
- scripts/edge-case-generator.py 6.9 KB runs code
- scripts/flaky-test-analyzer.py 4.9 KB runs code
- templates/dashboard.html 7.5 KB
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.
- 1mo ago First seen · 230 lines · 43 tokens per session scan A 89d8d5c87f8b
test-architect is a skill published in the GitHub repository wyattowalsh/agents (5 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 2,413 once invoked, about $0.0002 per session on Opus 5.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
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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.