Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. 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/hlalljie/agent-workflow-presets/main/.cursor/skills/testing/add-tests/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/add-tests)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/add-tests"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/add-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/hlalljie/agent-workflow-presets/add-tests"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/add-tests.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.00035 | $0.00986 |
| Opus 5.5 | $0.00014 | $0.00394 |
| Sonnet 5.5 | $0.00007 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
testing-add-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 22d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add tests
Job
Spawn a subagent to execute this skill. Write a test plan and create every artifact it names — Vitest files, snapshot/integration specs, smoke notes, and tests/manual/*.md when the change is visible to users. Mark each item [x] when that artifact exists. run tests executes what you listed here; this skill authors the plan and the tests.
Step 1 — Write the test plan
Think through the full, finished change — not just the current task — and decide what needs to be verified: behavior, edge cases, regressions, and anything a user would see in the browser. Some of those things need unit tests, some need integration or snapshot coverage, some only need a manual browser walkthrough, and some need nothing at all. Choose which categories apply — many things benefit from more than one (e.g. a derive function gets a unit test and the route using it gets a manual browser pass). Skip or mark N/A where a category genuinely does not apply.
Write this as a ### Test plan checklist in the task file (.cursor/plans/**/tasks/*.md), or in tests/plans/<slug>.md if there is no task file yet. Each row should name a concrete artifact: a file path under tests/, a tests/manual/*.md doc, or a smoke/build command. Use TEST-PLAN-TEMPLATE.md as a starting shape. Leave every item unchecked; you will [x] them as you finish Steps 2 and 3.
Step 2 — Implement automated tests
Create or update the unit, integration, snapshot, and smoke files the plan names, in the right places under tests/. See Reference below for naming conventions, suffixes, folder structure, and which category fits which kind of code. [x] each plan row when its file exists.
Step 3 — Author manual browser tests
If the change touches what users see — routes, components, shell, layout, charts, filters, navigation — the plan should already have a tests/manual/*.md row from Step 1. Author that file following write manual browser test and its TEMPLATE.md, then [x] the row. Running the checklist in a browser happens later inside run tests, not here.
What ships with it
1 file 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.
- 22d ago First seen · 55 lines · 35 tokens per session scan A 9bc91cfc59d3
testing-add-tests is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 35 tokens to every session and 986 once invoked, about $0.0001 per session on Opus 5.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-10-07.
Other skills, from other repositories
proof-of-work
Run the machine-verifiable gate (typecheck, test, lint, plus a screenshot for UI) so a diff is review-ready. Triggers "proof of work", "is this review-ready", "prove it is green".
cast-verify
Prove the work before calling it done, and leave the evidence where reviewers read it. Runs the repository's checks, exercises the change in the human's own browser or on the command line, captures screenshots or output, attaches them to the task and the thread, and only then marks the work done. Use before declaring…
e2e-check
Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
agentic-eval
Evaluate and improve AI-generated output with explicit rubrics, reflection loops, and stop conditions. Use when building self-critique workflows, evaluator-optimizer pipelines, or acceptance gates for code, docs, analysis, or plans.
skill-test
Testing framework for evaluating Databricks skills. Use when building test cases for skills, running skill evaluations, comparing skill versions, or creating ground truth datasets with the Generate-Review-Promote (GRP) pipeline. Triggers include "test skill", "evaluate skill", "skill regression", "ground truth", "GRP…