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 agentmods add commands/phuoctrung-ppt/ai-sdlc-workflow/generate-testgit clone --depth 1 https://github.com/phuoctrung-ppt/ai-sdlc-workflowWrote 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/phuoctrung-ppt/ai-sdlc-workflow/generate-test)<a href="https://agentmods.dev/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-test"><img src="https://agentmods.dev/badge/commands/phuoctrung-ppt/ai-sdlc-workflow/generate-test.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.00280 |
| Opus 5 | $0.00014 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
generate-test 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 4d 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.
What it actually says
Act as QA Worker. Generate tests for: {target}
Type: {unit|integration|e2e}
- Run context-builder:
python3 .cursor/context/context-builder.py \ --phase test --task "generate {type} tests for {target}" --agent qa-worker \ --keywords "test,mock,coverage,e2e,jest,vitest,playwright" - Read
.memory/constraints.mdandAGENTS.md §7(external services to mock)
Requirements:
- Read tier2
testing-qaSKILL.md; tier4 refs via--expand-refonly if needed - Mock all external services listed in
AGENTS.md §7(never hit real APIs in tests) - Multi-tenancy isolation cases if
AGENTS.md §5declares multi-tenancy - Follow naming convention from
AGENTS.md §2(e.g.*.spec.ts,*.test.ts,*.e2e-spec.ts) - Coverage target: 70%+ for service/business logic layers (see
AGENTS.md §6)
Output complete test file(s).
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.
- 4d ago First seen · 26 lines · 28 tokens per session scan A 107359714f75
generate-test is a command published in the GitHub repository phuoctrung-ppt/ai-sdlc-workflow (2 stars, last pushed 18d ago), licensed MIT. It adds 28 tokens to every session and 280 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.
test-suite
Run comprehensive test suite with coverage analysis.
testing
Comprehensive testing through distributed execution.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
test
🧪 Test Router — Route to testing workflows.