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-onboard/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-onboard)<a href="https://agentmods.dev/skills/shdra06/ai-mind-map/testsprite-onboard"><img src="https://agentmods.dev/badge/skills/shdra06/ai-mind-map/testsprite-onboard/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/shdra06/ai-mind-map/testsprite-onboard"><img src="https://agentmods.dev/badge/skills/shdra06/ai-mind-map/testsprite-onboard.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.00131 | $0.01783 |
| Opus 5 | $0.00066 | $0.00892 |
| Sonnet 5 | $0.00026 | $0.00357 |
| Haiku 4.5 | $0.00013 | $0.00178 |
Grade A, and why
testsprite-onboard 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 9d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestSprite: onboard a repo with a seed test suite
Your job is to take a repo that has no TestSprite tests yet and leave it with a coherent, runnable suite plus a couple of already-green smoke tests — in one pass. A new user who can immediately run a real, passing test is an activated user; an empty project is the #1 drop-off.
This skill only uses shipped CLI commands. It works the same whether the user is on the V2 or V3 backend — the CLI routes internally. Do not call backend APIs directly.
When to use
- Right after
testsprite setup, or any time the active project has 0–1 tests. - The user says "set up tests", "bootstrap", "seed a suite", "get me started", or similar.
When NOT to use
- The project already has tests — that's the
testsprite-verifyskill's job, not this one. - The user only changed code and wants it checked — again,
testsprite-verify.
Prerequisites
testsprite setup has run (an API key is configured). If testsprite project list errors on
auth, stop and tell the user to run testsprite setup first — don't try to configure for them.
Steps
1. Understand the app (don't skip — this is where coverage quality comes from)
Read the repo to establish, concretely:
- Frontend: the deployed/local URL, the 4–8 most important user flows (auth, core CRUD, checkout, search, settings…), and whether flows need login.
- Backend: the key API endpoints and their success/error contracts.
Prefer code-derived routes/handlers over guessing — you have the source; use it. This beats a blind crawl.
2. Create the project (FE must have a URL)
Frontend:
testsprite project create --type frontend --name "<repo name>" --url <app-url> \
[--username <user> --password-file <path-to-secret>]
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.
- 9d ago First seen · 169 lines · 131 tokens per session scan A 7a92ce14f2ad
testsprite-onboard is a skill published in the GitHub repository shdra06/ai-mind-map (1 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 1,783 once invoked, about $0.0007 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
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
browser-testing-with-devtools
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
agent-browser
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.