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/jonase47/ccprWrote 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/jonase47/ccpr/p3-infra-teststrategy)<a href="https://agentmods.dev/commands/jonase47/ccpr/p3-infra-teststrategy"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-teststrategy/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/jonase47/ccpr/p3-infra-teststrategy"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p3-infra-teststrategy.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.00000 | $0.00945 |
| Opus 5.5 | $0.00000 | $0.00378 |
| Sonnet 5.5 | $0.00000 | $0.00189 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
p3-infra-teststrategy 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p3-infra-teststrategy – Define Test Strategy
Defines test levels, test tools, coverage targets and critical test paths.
Argument: $ARGUMENTS = [Focus, e.g. "E2E", "Unit Tests", "Coverage"]
If provided: Deep-dive the named area. If not provided: Create complete test strategy.
Prerequisites
- ARCHITECTURE.md and TECH_STACK.md exist
- FEATURES.md with user journeys known
Agent
- Type: qa-tester
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and delivers inline:
- From FEATURES.md: Must-Have features (short list)
- From ARCHITECTURE.md: Modules and layers
- From TECH_STACK.md: Technologies in use (for tool recommendations)
- From USER_JOURNEYS.md: Critical flows (short list)
Prompt Template
Goal: Define test strategy for the project. Focus: $ARGUMENTS
Context: [inline from FEATURES.md, ARCHITECTURE.md, TECH_STACK.md]
Output Format:
- Test levels: Table | Level | What is tested | Who executes |
- Test tools: Table | Level | Tool | Justification |
- Coverage target: unit test coverage in % with justification (1 sentence)
- Critical test paths: Table | Flow | Test Level | Priority |
- Definition of Done for tests (max. 5 items)
Constraints:
- ONLY test strategy, NO infrastructure, NO monitoring
- Max. 4 test levels
- Max. 6 critical test paths
- Tools must be compatible with the tech stack
Orchestrator Checkpoint
- All test levels (unit, integration, E2E, exploratory) covered?
- Tools compatible with the tech stack?
Write Detail File
Write the result to docs/architecture/TESTSTRATEGY.md (overwrite if it exists). Start with this YAML frontmatter:
---
phase: P3
subskill: infra-teststrategy
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Test Levels, ## Test Tools, ## Coverage Target, ## Critical Test Paths, ## Definition of Done for Tests.
(File replaces the legacy TEST_STRATEGY.md name — keep the new TESTSTRATEGY.md going forward.)
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 Changed 59435bd9c685
- 1mo ago First seen · 93 lines · 0 tokens per session scan A 7790d018efc8
p3-infra-teststrategy is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 945 tokens. 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 commands, from other repositories
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
playwright-setup
Verify Playwright CLI installation and create a .playwright/cli.config.json configuration file. Use when setting up browser automation, configuring Playwright, or user mentions "setup playwright", "configure browser testing", "install playwright".
test
Run the project test suite. Reports results to .claude/runtime/outputs/sse/test/.
eval
Pick the eval judge. local = fresh Claude evaluator (default). jev = Jev by TypeSafe AI, needs API key.
zeus
A command that runs an automated software-building pipeline from a one-line product description through planning, implementation, review, Docker setup, and testing.
ccc-audit
Audit the current project for dependency vulnerabilities, oversized bundles, type errors, dead code, hardcoded secrets, undocumented env vars and a missing CLAUDE.md. Use when you want a health score before a release or review.