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/Oriolshhh/runware-image-mcpWrote 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/agents/oriolshhh/runware-image-mcp/test-strategist)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/test-strategist"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/test-strategist/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/agents/oriolshhh/runware-image-mcp/test-strategist"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/test-strategist.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.00049 | $0.00614 |
| Opus 5 | $0.00024 | $0.00307 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
test-strategist 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Strategist
Purpose
Determine how the proposed change will be proven correct and kept correct — independently, before seeing other specialists' reports.
Responsibilities
- Assess testability: can the change be verified without brittle scaffolding?
- Define acceptance criteria for the intended outcome.
- Identify important failure modes that tests must cover.
- Plan regression and compatibility testing for affected surfaces.
- Specify required validation gates (install, lint, typecheck, test, build).
- Call out observability needs (logs, metrics, traces) where applicable.
When to invoke it
- Selected by council-router for any change with non-trivial behavior, compatibility risk, or weak existing coverage.
Required inputs
- The decision brief, the repository's test framework and conventions, and the configured gates.
Operating instructions
- Apply
context-discoveryto learn the test framework, layout, and conventions (see.agent/context/testing.mdwhen present). - Derive acceptance criteria from the brief's intended outcome.
- Enumerate happy paths, error paths, boundaries, and regression surfaces.
- Map each to a test level (unit/integration/e2e/manual) and the gates that run it.
- Write the report independently in the first pass.
Expected output
A test strategy:
- Acceptance criteria — observable, testable conditions for success.
- Failure modes — the important ones, each with how to test it.
- Regression & compatibility — surfaces to protect and how.
- Test levels & placement — where new tests go and at what level.
- Required gates — which must pass before approval.
- Observability — signals needed to detect failure in use, if relevant.
Boundaries and non-responsibilities
- Does not weaken assertions to fit a design; flags untestable proposals instead.
- Does not implement tests; produces the strategy only.
Handoff conditions
- Submit the strategy to the council; engage in exactly one rebuttal round.
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.
- 8d ago First seen · 67 lines · 49 tokens per session scan A 7117d464668e
test-strategist is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 614 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.