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 faizkhairi/claude-code-blueprint --skill test-checkgit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/test-check)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/test-check"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/test-check.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 11 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00049 | $0.00548 |
| Opus 5 | $0.00024 | $0.00274 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
test-check 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.
What it actually says
Run the full test suite and provide analysis:
- Detect active project from current working directory or recent context:
- Check
CLAUDE.mdor the project manifest (package.json, pyproject.toml, Gemfile, pom.xml, etc.) for the test command - Common patterns:
yarn test:unit/npm test/npx vitest run(JS),pytest(Python),bundle exec rspec(Ruby),go test ./...(Go),mvn test(Java),cargo test(Rust),dotnet test(.NET) - Default (no context): ask which project
- Check
- Run the appropriate test command and capture output
- Report summary: total tests, passed, failed, skipped, duration
- If failures exist: analyze root cause of each failing test
- Compare against known baselines:
- Check
CLAUDE.mdfor the documented test baseline count for the active project - If no baseline is documented: parse the test summary output line for total count; compare against previous runs if agent memory has a baseline
- If actual count is higher than baseline, the test suite grew; if lower, investigate missing tests
- Check
- Check if recently modified files have corresponding tests
- Identify test coverage gaps for critical paths
- Suggest new tests if coverage is insufficient
- E2E tests (run if user says "e2e", "all", or "full"):
- Check
CLAUDE.mdfor the dev server port and E2E test command - Check if dev server is running on that port before proceeding
- Run E2E test command from
CLAUDE.md(e.g.,yarn test:e2eornpm run test:e2e, or the project's E2E command) - E2E baselines: documented in
CLAUDE.md - Parse the E2E runner's output (Playwright, Cypress, Selenium, Capybara, etc.): passed/failed/skipped counts
- On failure: note which spec file and test name failed
- If dev server is NOT running, report and skip (do NOT auto-start)
- Check
Present results in a clear dashboard format.
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 · 33 lines · 49 tokens per session scan A 61cc90c1f5f8
test-check is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 26d ago), licensed MIT. It adds 49 tokens to every session and 548 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-30.
Other skills, from other repositories
screen-reader-testing
Test web applications with screen readers including VoiceOver, NVDA, and JAWS. Use when validating screen reader compatibility, debugging accessibility issues, or ensuring assistive technology support.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
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.
dbt-transformation-patterns
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.