agentmods.dev

sk-create-manual-testing-playbook

sk-create-manual-testing-playbook is a skill for Claude Code, OpenCode from MichelKerkmeester/skilled-agent-harness_spec-driven-loops. It costs 27 tokens per session (6,017 once invoked), scanned A, original, MIT.

A workflow for creating repeatable manual testing playbooks with scenarios, evidence requirements, and pass-or-fail criteria.

In plain words
What is it for?
Use it to plan manual validation for skills, systems, command-line tools, tool interfaces, or multi-agent workflows.
Why use it?
It turns informal checklists into tests that another person or agent can reproduce and evaluate consistently.

Skill for Claude CodeOpenCode

Written for Claude Code and OpenCode: allowed-tools in frontmatter, but also installed under .opencode/. Also seen: mentions OpenCode.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node .opencode/skills/system-deep-loop/deep-improvement/scripts/skill-benchmark/run-skill-benchmark.cjs \.

not rated 35repo +1 changed 6d ago A scan SkillSpector: warn 27 tokens original MIT

Good fit Use it to plan manual validation for skills, systems, command-line tools, tool interfaces, or multi-agent workflows.

Compare 6 skills from other repositories ↓
View source ↗ MichelKerkmeester/skilled-agent-harness_spec-driven-loops
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loops
agentmods
npx agentmods add skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook

Made for: Claude Code, OpenCode.

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.

agentmods badge for sk-create-manual-testing-playbook

README.md
[![agentmods](https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook/github.svg)](https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook)
Your own site
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook/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.

agentmods 80×15 button for sk-create-manual-testing-playbook

Your own site · 80×15
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/sk-create-manual-testing-playbook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,017 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 8
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.06017
Opus 5 $0.00014 $0.03009
Sonnet 5 $0.00005 $0.01203
Haiku 4.5 $0.00003 $0.00602

Measured 6d ago against content hash 3295f8af59ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sk-create-manual-testing-playbook 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 6d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/tests/validate-playbook-package.test.cjs, scripts/validate-playbook-package.cjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.opencode/skills/sk-doc/sk-create-manual-testing-playbook/SKILL.md · 571 lines

How it starts

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

Manual Testing Playbook Creation

create-manual-testing-playbook is the manual-validation package workflow for the sk-doc family. It authors manual-testing-playbook/ packages for skills and systems that need reproducible operator-facing scenarios, evidence capture, release-readiness review, and realistic orchestration or multi-agent execution planning.

Core principle: keep shared rules in the root playbook, keep execution truth in per-feature files, and make every scenario deterministic enough that another operator can reproduce the verdict.

1. WHEN TO USE

Activation Triggers

Use this workflow when the request involves:

  • /create:manual-testing-playbook.
  • Creating manual-testing-playbook/manual-testing-playbook.md.
  • Building one-file-per-feature manual test scenarios.
  • Designing deterministic prompts, command sequences, expected signals, evidence, pass/fail criteria, and failure triage.
  • Planning manual validation across multiple operators, agents, CLIs, MCP tools, or runtime surfaces.
  • Converting an ad hoc release checklist into a reusable evidence-driven playbook package.
  • Aligning a manual testing playbook with a feature catalog.

Keyword triggers: manual testing playbook, /create:manual-testing-playbook, testing playbook, playbook system, deterministic scenario, evidence collection, operator validation, multi-agent execution, release readiness.

Strong signals that a playbook is warranted:

  • 5+ distinct features need manual validation.
  • Release decisions depend on structured evidence.
  • Realistic orchestration behavior matters.
  • Multiple operators or agents will execute the same scenarios.
  • Automated tests cover internals but not operator-visible behavior.

When NOT to Use

Use another sk-doc packet when:

Read the full file on GitHub · 571 lines

Files

What ships with it

25 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 6d ago Changed 3295f8af59ae
  2. 8d ago First seen · 571 lines · 27 tokens per session scan A 57a7beffec83

Subscribe to this mod's changes

sk-create-manual-testing-playbook is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 6,017 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-09-03.

Project managementTesting
Related

Other skills, from other repositories

scaffold-dotnet-test-project

MUST USE when an existing .NET test project was excluded from a .slnf/CI solution filter, disappeared from .sln/.slnx discovery, or lost its production ProjectReference; also for requests to set up, create, reuse, add, register, include, or repair a test project. Handles "tests pass directly but CI discovers zero"…

dotnet/skills · 139 tokens

cy-execute-task

Implement and verify an existing CompozyOS spec task, then update its tracking. Excludes review remediation.

compozy/compozy · 27 tokens

team-qa

Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.

Donchitos/Claude-Code-Game-Studios · 73 tokens

gh-issue

Size-audit, write, and split BanyanDB issues that somebody else or an automated TDD workflow can implement. Use whenever the user asks to file or revise an issue, decide whether an issue is too large, make an issue TDD-ready, turn a design into tickets, or split an umbrella into executable leaves. Do not draft or file…

apache/skywalking-banyandb · 91 tokens

implement-feature

Implement an approved feature plan with fresh-context slices, TDD, evidence, and PR-ready output.

HoangNguyen0403/agent-skills-standard · 23 tokens

conductor-implement

Execute tasks from a track's implementation plan following TDD workflow.

rmyndharis/antigravity-skills · 17 tokens