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 skills/gxfn/wakeflow/test-strategynpx skills add GxFn/Wakeflow --skill test-strategygit clone --depth 1 https://github.com/GxFn/WakeflowWrote 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/gxfn/wakeflow/test-strategy)<a href="https://agentmods.dev/skills/gxfn/wakeflow/test-strategy"><img src="https://agentmods.dev/badge/skills/gxfn/wakeflow/test-strategy.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.00041 | $0.00752 |
| Opus 5 | $0.00020 | $0.00376 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
test-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategy
Design the smallest real validation plan that answers the controller's question with credible evidence. This skill belongs to Test windows. It plans and collects evidence; it does not accept product work or dispatch follow-up implementation.
Source Skills Used
senior-qa: risky user journeys, test layer choice, must-pass automated tests, focused manual checklist, and flakiness as a product bug.code-reviewer: evidence should cover correctness, safety, maintainability, performance, and tests when relevant.- Industry basis: risk-based testing, test pyramid, and evidence confidence.
Wakeflow Role
Use this skill only when Test is justified by one of these:
- real project/environment verification;
- cold-start, dashboard, runtime, daemon, or monitoring observation;
- reproduction/regression that the controller cannot safely perform alone;
- cross-repository integration evidence;
- release or smoke confidence.
Do not use Test to rediscover defects already known to the controller or to run general QA without a boundary.
Required Inputs
- Controller test card or state-root reference.
- Exact question Test must answer.
- Target repository/window.
- What the controller/product window already self-verified.
- Success meaning.
- Failure meaning.
- Invalid conclusions.
- Stop conditions.
If those inputs are missing, stop and report missing test boundary evidence.
Workflow
- Restate the question.
- What decision will this evidence enable?
- What must not be concluded from this run?
- Map risk.
- Critical user journey.
- Money/auth/data loss/privacy/security risk.
- Integration boundary.
- Runtime or environment dependency.
- Known flaky area.
- Choose test layer.
- Unit for isolated logic.
- Integration for boundary behavior.
- E2E/manual for key user-visible or environment-dependent paths.
- Runtime/log/dashboard observation only when the question needs real operational evidence.
- Define evidence.
- Commands.
- Reports, logs, screenshots, runtime JSON, or traces.
- Expected pass/fail signal.
- Re-run or flake handling rule.
- Run only the agreed boundary.
- Return evidence and interpretation without accepting product completion.
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 · 120 lines · 41 tokens per session scan A a99e86a7e920
test-strategy is a skill published in the GitHub repository GxFn/Wakeflow (5 stars, last pushed 11d ago), licensed MIT. It adds 41 tokens to every session and 752 once invoked, about $0.0002 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 skills, from other repositories
fleet
Parallel campaign orchestrator. Runs multiple campaigns in coordinated waves within a single session. Spawns 2-3 agents per wave in isolated worktrees, collects discoveries, shares context between waves. Use when work decomposes into 3+ independent streams that can run simultaneously.
archon
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
daemon
Continuous autonomous operation mode. Keeps campaigns running 24/7 by chaining Claude Code sessions via RemoteTrigger. Each session picks up from the campaign's continuation state, works until context runs low or the phase completes, then schedules the next session. Auto-stops on campaign completion or budget…
dashboard
Real-time harness observability dashboard. Reads campaigns, fleet sessions, telemetry, and pending queues to present a snapshot of harness state at a glance. Invoked by /dashboard, /do status, or phrases like "what's happening" and "show activity".
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…