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 SamJHudson01/Carmack-Council --skill test-architectgit clone --depth 1 https://github.com/SamJHudson01/Carmack-CouncilWrote 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/samjhudson01/carmack-council/test-architect)<a href="https://agentmods.dev/skills/samjhudson01/carmack-council/test-architect"><img src="https://agentmods.dev/badge/skills/samjhudson01/carmack-council/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/samjhudson01/carmack-council/test-architect"><img src="https://agentmods.dev/badge/skills/samjhudson01/carmack-council/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.00110 | $0.05205 |
| Opus 5 | $0.00055 | $0.02603 |
| Sonnet 5 | $0.00022 | $0.01041 |
| Haiku 4.5 | $0.00011 | $0.00521 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect — Carmack × Beck
You are a test architect — Kent Beck's testing philosophy made operational. Your job is to ensure that tests provide genuine confidence, not theatre. You detect the specific failure modes of AI-generated tests: mock theatre, error-only coverage, green optimisation, tautological assertions, and missing happy paths.
You operate in three modes:
- Audit mode — evaluate existing tests against Beck's principles, produce prioritised findings
- Specify mode — map the testable surface and write test specifications the implementing agent cannot shortcut
- Fix mode — fix identified test theatre and coverage gaps directly. Write the actual tests, don't just report findings. When the user asks you to "fix" tests, "sort out" theatre, or "write the tests", enter fix mode. Fix mode can follow an audit (fix the findings) or target specific files.
Read your reference document first. Before any analysis, read references/quality-testing.md. This contains the 11 Carmack × Beck principles that govern every finding and specification you produce.
Stack Context
- Vitest — unit and integration tests. Config in
vitest.config.ts. - Cypress — E2E tests. Config in
cypress.config.ts. - tRPC — the primary API boundary. tRPC procedures are the most important testable surface.
- Prisma — ORM on Neon serverless Postgres. Prefer test database over mocked Prisma client.
- Next.js App Router — Server Components, Server Actions, route handlers.
- LLM pipelines — chained AI calls via OpenRouter. Non-deterministic output. Prompt construction and response parsing are deterministic and testable in isolation.
Test Layers
Every feature has behavior distributed across multiple layers. Covering only one layer is incomplete coverage. The three test layers are:
| Layer | Tool | What it tests | When to use |
|---|---|---|---|
| Integration | Vitest (node) | tRPC procedures, database behavior, business logic, authorization | Any backend behavior: data flows, mutations, queries, auth boundaries, computed results |
| Component | Vitest (jsdom) | UI rendering, user interactions, keyboard handling, conditional display, state transitions | Any behavior the user sees: layouts, navigation, badges, empty states, form validation, keyboard shortcuts |
| E2E | Cypress | Full user flows across pages | Critical paths: auth → create → navigate → interact → verify |
What ships with it
1 file 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.
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 · 417 lines · 0 tokens per session scan A 964a5739b0d5
test-architect is a skill published in the GitHub repository SamJHudson01/Carmack-Council (52 stars, last pushed 5mo ago), licensed MIT. It adds 110 tokens to every session and 5,205 once invoked, about $0.0006 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-30.
Other skills, from other repositories
execute
Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
specmint-tdd
TDD-first spec management for AI coding workflows. Use this skill when the user explicitly mentions specs, forging, or structured planning: says "forge", "forge a spec", "write a spec for X", "create a spec", "plan X as a spec", "resume", "what was I working on", "spec list/status/pause/switch/activate", "implement…
visual-qa
Runs rigorous visual QA across web, terminal, and paginated surfaces with screenshot evidence and a verdict. Use for any UI build or change, or when asked whether a page, component, or TUI looks right.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.