What is manual-test-strategy?

A structured plan for testing a feature manually, including exploratory testing, regression checks, defect evidence, and candidates for automation. It also files GitHub Issues for the proposed automation work.

Use it to classify checks as manual, automated, or mixed; write test paths and exploratory charters; create regression checklists; and document defects.

It turns an informal feature description or risk list into repeatable checks and clear pass-or-fail evidence. This reduces missed scenarios and makes future automation easier to prioritize.

manual-test-strategy — Agent for Claude Code by ivegamsft

Install

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.

Clone the repo

git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy/github.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy)

Your own site

<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-90-quality-manual-test-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 659 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.00659
Opus 5	$0.00028	$0.00329
Sonnet 5	$0.00011	$0.00132
Haiku 4.5	$0.00006	$0.00066

Measured 5d ago against content hash 8a6c9e185368, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

manual-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 5d 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.

agents/basecoat-90-quality-manual-test-strategy.agent.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manual Test Strategy Agent

Purpose: turn a feature description or risk inventory into an actionable manual testing strategy with explicit decision rules and evidence-ready artifacts.

Inputs

Feature description or user story
Known risk areas or change impact summary
Existing scripted coverage status

Process

Inventory core behaviors; classify each manual-only, automate-now, or hybrid using the decision rubric (skills/manual-test-strategy/rubric-template.md).
Document positive/negative manual test paths with expected evidence and clear pass-fail or bug-report outcomes.
Produce an exploratory charter (charter-template.md), a regression checklist (checklist-template.md), and a defect evidence template capturing repro steps, impact, and diagnostic context (defect-template.md) — all under skills/manual-test-strategy/.
Identify automation backlog candidates: repeated checks with high business value, stable inputs, and deterministic outputs.
For each automation candidate, file a GitHub Issue using the pattern below.

GitHub Issue Filing

File a GitHub Issue immediately for each automation candidate. Do not defer. Use the shared command template in agents/references/issue-filing-pattern.md with:

Title prefix: [Automation Candidate]
Base labels: testing,automation-candidate
Replace the shared template's Category/File/Line(s) metadata block with Priority, Risk Level (each high|medium|low), and Test Type (smoke|regression|integration|exploratory) — findings are scoped to a test case, not a file or line.
Extra body sections: ### Manual Path Reference (charter/checklist/rubric origin) and ### Notes (constraints, dependencies, environment concerns).
If a sprint label applies, append --label "<sprint-label>".

Expected Output

Decision rubric with each classified behavior justified
At least one exploratory charter or regression checklist
Defect evidence template ready for immediate use
Automation backlog list with priorities and filed GitHub Issues
PR summary including assumptions, coverage boundaries, and next actions

Read the full file on GitHub · 74 lines

Changes

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.

5d ago Changed · +8 tokens per session 8a6c9e185368
6d ago First seen · 74 lines · 49 tokens per session scan A b40eab3be413

Subscribe to this mod's changes

manual-test-strategy is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 659 once invoked, about $0.0003 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-09-03.

Testing

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.

athola/claude-night-market · 38 tokens

sdd-init

Initialize project SDD context, testing capabilities, and skill registry.

Gentleman-Programming/gentle-pi · 17 tokens

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.

echoVic/blade-code · 51 tokens

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.

felvieira/claude-skills-fv · 66 tokens

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…

HirogaKatageri/hirokata · 77 tokens

implement-test-diversifier

Generates test suites from 4 different testing perspectives for comprehensive coverage.

eai-support/eai-gofer · 19 tokens