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 justnau1020/claude-os --skill test-allgit clone --depth 1 https://github.com/justnau1020/claude-osWrote 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/justnau1020/claude-os/test-all)<a href="https://agentmods.dev/skills/justnau1020/claude-os/test-all"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/test-all/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/justnau1020/claude-os/test-all"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/test-all.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.00029 | $0.00381 |
| Opus 5.5 | $0.00012 | $0.00152 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
test-all 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 1mo 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 Full CI Pipeline
Run the complete CI pipeline locally in the same order as CI/CD.
Pipeline Steps (run in order, stop on first failure)
1. Lint
Run the project's linter. Examples:
# Python
ruff check {source_dir}/ tests/
# JavaScript/TypeScript
npx eslint src/
If there are auto-fixable issues, report them but do NOT auto-fix unless asked. Show the exact errors.
2. Type check
Run the project's type checker. Examples:
# Python
mypy {source_dir}/ --ignore-missing-imports
# TypeScript
npx tsc --noEmit
Report any type errors with file paths and line numbers.
3. Run test suite
# Python
pytest tests/ -v --tb=short
# JavaScript/TypeScript
npm test
If $ARGUMENTS is provided, pass it as additional arguments:
pytest tests/ -v --tb=short $ARGUMENTS
Reporting
After all steps complete, provide a summary:
CI Pipeline Results:
Lint: PASS/FAIL (N issues)
Types: PASS/FAIL (N errors)
Tests: PASS/FAIL (N passed, N failed, N skipped)
If any step fails, explain what failed and suggest specific fixes. Include file paths and line numbers for all failures.
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.
- 1mo ago First seen · 67 lines · 29 tokens per session scan A f8d91481bb25
test-all is a skill published in the GitHub repository justnau1020/claude-os (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 381 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-08-31.
Other skills, from other repositories
spring-boot-team-harness
Use when a team wants every developer's coding agent (Claude Code or Codex) to follow the same rules on a Maven Spring Boot 4 repository: setting up AGENTS.md, guardrails, shared agent settings, or build and CI checks that agents must pass before code merges. It adds ./mvnw verify gates that fail on null-safety bugs…
ci-cd
Use when building or fixing a delivery pipeline. Covers pipeline structure, caching, test parallelization, deployment strategies, secrets, and making the pipeline fast enough that people do not route around it. Trigger on "our ci takes 40 minutes", "flaky pipeline keeps failing", "set up github actions to deploy". Do…
init-pipeline
Infrastructure skill for scaffolding pipeline enforcement into a project. Sets up Claude Code hooks (TDD classification gate, git guardrails, optional quality gate), pre-commit hooks (detects existing tools, defaults to Lefthook + Biome + pnpm if none found). Run when setting up a project for pipeline work, and again…
ci-test-orchestration
When the user wants to design, audit, or optimize how tests run in CI — sharding, matrix builds, parallelism, retry policy, test selection, artifact handling, and gate strategy. Use when the user mentions "CI test orchestration," "test sharding," "matrix builds," "parallel tests in CI," "GitHub Actions matrix,"…
running-tests
Runs tests and handles failures. Triggered when: test execution, verification, test failures, CI checks.
testing-automation-expert
Production-grade testing strategies for robust, maintainable systems. Covers unit/integration/E2E testing, contract testing, accessibility, mutation testing, and CI/CD patterns. Supports Python (pytest) and TypeScript (Jest/Vitest/Playwright).