Borrowing it
Nothing to install: this file belongs to shdra06/ai-mind-map. 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/shdra06/ai-mind-map/main/.agents/skills/testsprite-verify/SKILL.mdgit clone --depth 1 https://github.com/shdra06/ai-mind-mapWrote 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/shdra06/ai-mind-map/testsprite-verify)<a href="https://agentmods.dev/skills/shdra06/ai-mind-map/testsprite-verify"><img src="https://agentmods.dev/badge/skills/shdra06/ai-mind-map/testsprite-verify.svg" alt="Measured on agentmods" 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.00105 | $0.05675 |
| Opus 5 | $0.00053 | $0.02838 |
| Sonnet 5 | $0.00021 | $0.01135 |
| Haiku 4.5 | $0.00011 | $0.00568 |
Grade A, and why
testsprite-verify scanned grade A with 1 finding 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.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
r = requests.post(f"{TARGET_URL}/login", json={"email": "[email protected]", "password": ""}) How it starts
The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestSprite Verification Loop
The verification loop that flies your just-shipped feature through the TestSprite CLI and reports back.
You just finished a piece of work in a TestSprite-tested repo. Before you report
it done, actually run the relevant TestSprite test(s) through the testsprite
CLI and read the result. Spec review and unit tests catch correctness; only
running the test catches what breaks for a real user.
When to run
Run after a feature or fix lands — one feature → one test run, at the moment it
lands, not batched at the end. Tests you create this way accumulate into the
project's TestSprite suite; before writing a new one, check testsprite test list
for an existing test that already covers the behavior and extend it instead of
duplicating.
The CLI tests a deployed URL — it doesn't build or host your environment.
Run the loop only once the change is live somewhere reachable (e.g. open the PR,
let CI deploy the preview/staging environment) and pass that URL as
--target-url. Running earlier verifies the previous build, not your change.
When to skip
The skip list is narrow:
- Docs-only edits (
docs/**,*.md, comments). - Pure build/config edits (
tsconfig*, lint/prettier config, lockfile bumps with no behavior change). - This repo isn't actually wired to TestSprite (no project linked, no creds). Don't pull the user into a setup flow they didn't ask for — say so and stop.
Otherwise, run it.
The one-test minimum
Every shipped feature gets at least one TestSprite run to a terminal verdict
(passed / failed / blocked / inconclusive) before you call it done. What
counts:
testsprite test create … --run --waitreturning a terminal verdict, ortestsprite test run <id> --waitagainst an existing test, ortestsprite test create-batch --plans plans.jsonl --run --wait(or two-step: create-batch, thentest run <id> --wait) on at least one test returning a terminal verdict.
What does not count: unit tests / typecheck / lint; drafting a plan without
--run; asking the user to run it for you.
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.
- 6d ago First seen · 448 lines · 105 tokens per session scan A 0954cc6c58e0
testsprite-verify is a skill published in the GitHub repository shdra06/ai-mind-map (1 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 5,675 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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-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…
e2e-runner
End-to-end testing specialist using Vercel Agent Browser or Playwright.
e2e-tests
Tests E2E Playwright pour SaaS Next.js : setup, Page Object Model, auth state, flows critiques (login, billing, onboarding), CI GitHub Actions.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.