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 fanfan-de/anybox --skill smarter-testinggit clone --depth 1 https://github.com/fanfan-de/anyboxWrote 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/fanfan-de/anybox/smarter-testing)<a href="https://agentmods.dev/skills/fanfan-de/anybox/smarter-testing"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/smarter-testing/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/fanfan-de/anybox/smarter-testing"><img src="https://agentmods.dev/badge/skills/fanfan-de/anybox/smarter-testing.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.00080 | $0.01017 |
| Opus 5 | $0.00040 | $0.00508 |
| Sonnet 5 | $0.00016 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
circleci-smarter-testing 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 8d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CircleCI Smarter Testing
Overview
Beta (Discuss). Create or adjust .circleci/test-suites.yml, wire it into CI, and validate with --doctor until checks pass. Let doctor diagnose YAML, command, JUnit, and testsuite errors before adding extra guidance.
Doctor command (required)
The testsuite CLI uses Bubble Tea and must run with a TTY. When iterating with --doctor, the agent must always run this exact command (substitute the suite name only):
script -q /dev/null circleci run testsuite "<suite name>" --doctor
Do not modify this command: no pipes, tail, redirects, backgrounding, or truncation.
Scope: testsuite setup and validation. Not legacy circleci tests run / timings-only JUnit tuning → circleci-config (test-results-and-splitting.md). Primary doc: Getting started.
Lazy references: read only what the task needs—do not load every reference file up front.
- Runner YAML → references/runners.md (matching section only)
- CI /
store_test_results→ references/ci-and-junit.md - TIA, splitting, auto-rerun → references/optional-features.md
Inputs To Gather
- Runner, test root, existing
.circleci/config.yml - Optional: TIA, dynamic splitting, auto-rerun limits
- Hand off:
circleci-cli(install/auth/plugin) |circleci-config(JUnit/circleci tests runwithout testsuite) |circleci-builds(CI fails after doctor-clean config)
Workflow
- Inspect — runner, layout, existing CI; reuse documented test commands; run testsuite from the test root (no
cdin YAML). - Baseline —
.circleci/test-suites.ymlwithname,discover,run,outputs.junit(see runners.md). - Doctor — run the exact command above; apply its guidance; repeat until pass.
- Local vs CI — Local needs CLI + testsuite plugin (
brew install circleci/tap/circleci-testsuiteon macOS; binaries on Linux/WSL). CI usescircleci run testsuiteon executors + ci-and-junit.md. - Optional features — only if asked; see optional-features.md; doctor after each change.
- Verify — full
circleci run testsuite "<suite name>"; optional TIA/rerun checks per docs.
What ships with it
3 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.
- 8d ago First seen · 65 lines · 80 tokens per session scan A b2f847d0ce4c
circleci-smarter-testing is a skill published in the GitHub repository fanfan-de/anybox (57 stars, last pushed 28d ago), licensed MIT. It adds 80 tokens to every session and 1,017 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipeline...
Checkly Monitoring as Code
Teach agents to build synthetic monitoring as code with Checkly, including Playwright browser checks, API checks, alerting, and CI deploy workflows.
CI Test Sharding Parallelization
Teach agents to shard and parallelize Playwright, Jest, and pytest suites in CI to reduce wall-clock time while merging reports reliably.