ODS is a system for turning a PC, Mac, or Linux computer into a private local AI server, meaning a machine that runs models and related AI services itself. It supports local model inference, chat, voice, agents, workflows, document retrieval, search, and image generation. The catalogue includes commands and an instruction for operating or configuring this system.
Borrowing it
Nothing to install: this file belongs to Osmantic/ODS. 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/Osmantic/ODS/main/.claude/commands/test-coverage.mdgit clone --depth 1 https://github.com/Osmantic/ODSWrote 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/commands/osmantic/ods/test-coverage)<a href="https://agentmods.dev/commands/osmantic/ods/test-coverage"><img src="https://agentmods.dev/badge/commands/osmantic/ods/test-coverage/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/commands/osmantic/ods/test-coverage"><img src="https://agentmods.dev/badge/commands/osmantic/ods/test-coverage.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.00000 | $0.03856 |
| Opus 5.5 | $0.00000 | $0.01542 |
| Sonnet 5.5 | $0.00000 | $0.00771 |
| Haiku 4.5 | $0.00000 | $0.00386 |
Grade A, and why
test-coverage 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 2mo 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 — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Coverage Updater
Analyze current test coverage, identify gaps, and write missing tests to improve coverage across both Shell (BATS) and Python (pytest) test suites.
Arguments
$ARGUMENTS- Options to control scope and behavior:--type=shell|python|dashboard|all- Test type to focus on (default:all)--target=N- Coverage percentage target for Python (default:80); shell uses structural coverage--module=<name>- Restrict to a specific module (e.g.,tier-map,helpers,routers.setup)--dry-run- Analyze gaps and report plan without writing tests--fix- Fix failing existing tests before writing new ones
Test Type Definitions
| Type | Location Pattern | What It Tests | Run Command |
|---|---|---|---|
| Shell unit (BATS) | tests/bats-tests/<lib>.bats |
Installer lib functions in isolation | bats tests/bats-tests/<lib>.bats |
| Shell integration | tests/test-<feature>.sh |
Multi-module shell interactions | bash tests/test-<feature>.sh |
| Shell contract | tests/contracts/test-*.sh |
Installer contract assertions | bash tests/contracts/test-*.sh |
| Shell smoke | tests/smoke/<platform>.sh |
Platform-specific end-to-end | bash tests/smoke/<platform>.sh |
| Python unit | dashboard-api/tests/test_<module>.py |
FastAPI routers, helpers, security | pytest tests/test_<module>.py |
| Dashboard UI | dashboard/src/**/*.test.* |
React component tests (if present) | npm test (in dashboard/) |
Philosophy: Ask Early, Ask Often
This skill should liberally use AskUserQuestion at decision points. Test coverage involves tradeoffs between speed and thoroughness. Validate priorities rather than guessing what the user wants covered.
- Before writing tests — confirm which modules to prioritize
- When gaps are large — ask where to focus effort first
- After coverage run — ask about iteration vs stopping
- When source code looks buggy — ask before fixing vs just testing
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.
- 2mo ago First seen · 485 lines · 0 tokens per session scan A e4b085bbdfcf
test-coverage is a command published in the GitHub repository Osmantic/ODS (7,712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,856 tokens. 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 commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
check
View the latest screenshot from /Pictures/Screenshots.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
tdd
Test-driven change — write the failing test first, then implement.
story-and-test
For the component(s) in scope.
fire-test
Run Dominion Flow plugin integration tests to verify all commands and integrations work correctly.