Borrowing it
Nothing to install: this file belongs to Federico-Anastasi/DYLA-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Federico-Anastasi/DYLA-ai/main/.agents/skills/test-plan/SKILL.mdgit clone --depth 1 https://github.com/Federico-Anastasi/DYLA-aiWrote 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/federico-anastasi/dyla-ai/test-plan)<a href="https://agentmods.dev/skills/federico-anastasi/dyla-ai/test-plan"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/test-plan/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/federico-anastasi/dyla-ai/test-plan"><img src="https://agentmods.dev/badge/skills/federico-anastasi/dyla-ai/test-plan.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.00040 | $0.02115 |
| Opus 5 | $0.00020 | $0.01058 |
| Sonnet 5 | $0.00008 | $0.00423 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
test-plan 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 11d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/test-plan — Test plan
The test plan is the list of cases the team runs before delivery. It does two jobs: it verifies the application does what the brief promised, and it proves it to the client.
The material is all there already: the estimate says what was built, the mockup says how it is used, the brief says what should happen.
UX: chat stays conversational. Never paste the test cases into chat: the user reads them in the viewer. In chat you talk about coverage and areas, citing cases by id and title (e.g. "TC12, the import with rejected rows").
PROTOCOL
- Check dependencies — a confirmed estimate is required
- Read the estimate, mockup, data model, brief and context.md
- If the test plan exists: ask whether to update or regenerate it
- Write test_plan.json straight away with
meta.status: "draft" - Say in words what is covered and what is not (BLOCKING)
- On confirmation:
meta.status: "confirmed" - Update context.md
PHASE 1 — CHECK DEPENDENCIES
Read projects/{project}/estimate.json. If it does not exist, stop:
Writing the test plan needs the estimate: the epics it measures coverage against come
from there. Produce it first with /estimate.
If it exists but meta.status is "draft", say the cases will need revisiting once the
estimate settles, then carry on: waiting gains nothing, most of the cases will not change.
PHASE 2 — READING
Read ALL of these before you go on:
projects/{project}/estimate.json— the epics and tasks: the skeleton of the coverageprojects/{project}/mockup.json— if it exists: pages, fields, actions, dialogsprojects/{project}/data_model.json— if it exists: the entities and constraints to verify- the brief:
projects/{project}/brief.json, or the input document (or its extract under.extracted/) projects/{project}/context.md— decisions and assumptionsprojects/{project}/test_plan.json— if it existsknowledge/— if the folder exists: house test conventions, client requirements
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.
- 11d ago First seen · 192 lines · 40 tokens per session scan A 6b313c89078d
test-plan is a skill published in the GitHub repository Federico-Anastasi/DYLA-ai (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 2,115 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
flame-harness-evaluator
Phase 6 — skeptical QA. Run the game, watch it, then judge against the contract. Default = functional check; --strict adds quality and edge-case passes.
fabrik-validate
Use when operating as the Fabrik Validate stage agent. This skill guides final validation of an implementation, verifying requirements are met, tests pass, and the PR is ready to merge.
coding-quality-loop
Use when a coding agent must turn a software goal, bug, issue, or refactor into a small, verified, independently reviewed code change.
test-integrity-gate
Use when AI-written code or tests claim green and you need deterministic proof that the new test catches the old bug.
e2e-testing
Use when writing or maintaining end-to-end tests — Playwright (preferred) or Cypress critical-flow suites. Pattern playbook: page objects, stable selectors, fixtures and isolation, condition-based waiting, flaky quarantine, CI wiring. Backs the e2e-runner agent.
agent-evaluation
This skill should be used when the user asks to "evaluate agent performance", "build test framework", "measure agent quality", "create evaluation rubrics", "implement LLM-as-judge", "compare model outputs", "mitigate evaluation bias", or mentions multi-dimensional evaluation, agent testing, quality gates, direct…