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 skills add jaktestowac/awesome-copilot-for-testers --skill designing-functional-testsgit clone --depth 1 https://github.com/jaktestowac/awesome-copilot-for-testersWrote 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/jaktestowac/awesome-copilot-for-testers/designing-functional-tests)<a href="https://agentmods.dev/skills/jaktestowac/awesome-copilot-for-testers/designing-functional-tests"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/designing-functional-tests/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/skills/jaktestowac/awesome-copilot-for-testers/designing-functional-tests"><img src="https://agentmods.dev/badge/skills/jaktestowac/awesome-copilot-for-testers/designing-functional-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00059 | $0.01343 |
| Opus 5 | $0.00030 | $0.00672 |
| Sonnet 5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
designing-functional-tests 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 10d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designing Functional Tests
Use this skill when the goal is to turn product intent into tester-ready coverage rather than directly generating automation. It helps produce plans and cases that are clear enough for manual execution and clean enough to hand off to automation later.
When to Use
- create a risk-based functional test plan
- turn acceptance criteria into manual test cases
- convert exploratory notes into reusable scenario packs
- prepare a regression slice for a bug fix or small feature
- identify which scenarios should move into automated tests first
Core Rules
- No silent invention - missing behavior becomes a question or an explicit assumption.
- Risk decides depth - high-risk flows deserve positive, negative, boundary, permission, and recovery coverage.
- One case proves one thing - avoid giant cases that validate five behaviors at once.
- Stable IDs matter - use durable IDs for scenarios and cases so they can be referenced later.
- Manual first, automation second - good automation starts with stable, observable manual intent.
Workflow
Phase 0: Frame the deliverable
Decide which artifact is needed:
- Full plan - scope, priorities, scenario catalog, risks, open questions
- Manual cases - detailed steps and expected results
- Regression slice - the smallest believable retest pack after a change
If the user did not specify the artifact, choose the lightest format that still solves the task.
Phase 1: Run the test-readiness gate
Before writing cases, confirm the test basis gives enough signal to work with.
Minimum signal:
- the feature or flow being tested
- the actor or user role
- the starting state or preconditions
- an observable success outcome
If any of these are missing:
- Ask targeted questions.
- If the user wants to move fast, proceed with an Assumptions section instead of inventing hidden requirements.
- Tag affected scenarios or cases with
ASSUMPTION.
Do not write confident-looking expected results for behavior that is still unknown.
What ships with it
2 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.
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.
- 10d ago First seen · 174 lines · 59 tokens per session scan A 61fb2fadba30
designing-functional-tests is a skill published in the GitHub repository jaktestowac/awesome-copilot-for-testers (113 stars, last pushed 14d ago), licensed MIT. It adds 59 tokens to every session and 1,343 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-08-30.
Other skills, from other repositories
winui-ui-testing
Automated UI testing for Windows desktop apps — generate a batch test script with the winapp ui UI Automation harness, run all tests in one pass, read results. Covers element assertions, interactions, value checking (TextBox, ComboBox, ToggleSwitch), keyboard shortcuts and typing (send-keys), hover, drag-and-drop…
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
ui-aqa-flow
Workflow for automated QA: integration and end-to-end UI test automation, page objects, etc.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
playwright-testing
Generer og kjør Playwright E2E-tester for webapplikasjoner med page objects, auth fixtures og tilgjengelighetstester.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions…