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.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote 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/commands/navraj007in/architecture-cowork-plugin/generate-tests)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/generate-tests"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/generate-tests/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/commands/navraj007in/architecture-cowork-plugin/generate-tests"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/generate-tests.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.00020 | $0.03089 |
| Opus 5 | $0.00010 | $0.01545 |
| Sonnet 5 | $0.00004 | $0.00618 |
| Haiku 4.5 | $0.00002 | $0.00309 |
Grade A, and why
generate-tests 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 11d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:generate-tests
Trigger
/architect:generate-tests — generate all test types (default).
/architect:generate-tests [type:X] — generate one test type only.
/architect:generate-tests [types:X,Y] — generate a named subset.
Test types
| Type | What it generates |
|---|---|
unit |
Unit tests per module (pure functions, services, utils) |
integration |
Integration tests per service (DB, API, queue interactions) |
e2e |
End-to-end tests per critical user flow |
Examples:
/architect:generate-tests [type:unit]
/architect:generate-tests [types:unit,integration]
/architect:generate-tests [type:e2e] [non_interactive:true]
When a [type:...] or [types:...] tag is present, generate only the named test types and skip all others. When absent, generate all types.
Options
[non_interactive:true]— skip all questions, derive from SDL and existing project[coverage_target:NN]— override coverage target (default: 80)
Purpose
After /architect:scaffold creates a project, services have no test coverage. This command generates production-ready test suites with unit tests (per module), integration tests (per service), and e2e tests (per critical flow). Scaffolds follow testing-strategy skill conventions: AAA structure, mock patterns, fixture setup, and coverage thresholds by stage.
Workflow
Quick Navigation
| Phase | Steps |
|---|---|
| Setup | Step 1 · Step 1.5 |
| Configuration | Step 2 · Step 2.5 |
| Generation | Step 3 · Step 3.5 |
| Completion | Step 4 · Step 4.5 · Step 5 |
Step 1: Read Context & Check for Scaffolded Project
ℹ️ CONTEXT LOADING: _state.json → SDL → scaffolded components
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.
- 11d ago First seen · 311 lines · 20 tokens per session scan A 0c5af1c1be61
generate-tests is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 3,089 once invoked, about $0.0001 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.
Other commands, from other repositories
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
verify
Verify a repository in fast or full mode with runner-first execution, deterministic stage order, and explicit PASS/FAIL/SKIP output.
sdlc-test
Generate and run multi-tiered enterprise test suites (Unit, Integration, E2E, Contract, Load/k6, Chaos, and Fuzz testing).
spec-verify
Run post-deployment smoke tests against a live environment.
mockless-tests-block
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
add-tests
Generate comprehensive tests for a component or API endpoint.