Borrowing it
Nothing to install: this file belongs to affandar/duroxide. 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/affandar/duroxide/main/.github/skills/duroxide-code-coverage/SKILL.mdgit clone --depth 1 https://github.com/affandar/duroxideWrote 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/affandar/duroxide/duroxide-code-coverage)<a href="https://agentmods.dev/skills/affandar/duroxide/duroxide-code-coverage"><img src="https://agentmods.dev/badge/skills/affandar/duroxide/duroxide-code-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/skills/affandar/duroxide/duroxide-code-coverage"><img src="https://agentmods.dev/badge/skills/affandar/duroxide/duroxide-code-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.00042 | $0.00697 |
| Opus 5.5 | $0.00017 | $0.00279 |
| Sonnet 5.5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
duroxide-code-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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Duroxide Code Coverage
Guidance for measuring and improving code coverage in the Duroxide codebase.
Quick Commands
# Summary (recommended for quick checks)
cargo llvm-cov nextest -p duroxide --all-features --summary-only
# Detailed per-file report
cargo llvm-cov nextest -p duroxide --all-features
# HTML report (opens in browser)
cargo llvm-cov nextest -p duroxide --all-features --html --open
# Install llvm-cov if needed
cargo install cargo-llvm-cov
Coverage Targets
| Metric | Target | Notes |
|---|---|---|
| Lines | >90% | Primary metric |
| Regions | >85% | Branch coverage |
| Functions | >80% | Often lower due to unused helpers |
Priority Files
When coverage drops, focus on these files:
- src/providers/error.rs - Target 100%, error classification
- src/runtime/observability.rs - Target 90%, metrics correctness
- src/providers/sqlite.rs - Target 85%, reference implementation
- src/providers/instrumented.rs - Target 75%, observability wrapper
- src/providers/management.rs - Note: default trait impls inflate gaps
Adding Tests
| Gap Type | Location |
|---|---|
| Management API | tests/coverage_improvement_tests.rs |
| Provider validation | tests/sqlite_provider_validations.rs |
| Observability | tests/observability_tests.rs |
| SQLite edge cases | src/providers/sqlite.rs (inline tests) |
Test Patterns
Management API
#[tokio::test]
async fn test_management() {
let store = Arc::new(SqliteProvider::new_in_memory().await.unwrap());
let mgmt = store.as_management_capability().unwrap();
assert!(mgmt.list_instances().await.is_ok());
}
Metrics
#[tokio::test]
async fn test_metrics() {
use duroxide::runtime::observability::{MetricsProvider, ObservabilityConfig};
let metrics = MetricsProvider::new(&ObservabilityConfig::default()).unwrap();
metrics.record_orchestration_failure("Orch", "1.0", "app_error", "cat");
assert_eq!(metrics.snapshot().orch_application_errors, 1);
}
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 · 94 lines · 42 tokens per session scan A 84a415306095
duroxide-code-coverage is a skill published in the GitHub repository affandar/duroxide (21 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 697 once invoked, about $0.0002 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-30.
Other skills, from other repositories
implement
Execute tasks from track plan with TDD workflow and git commit integration.
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccganalyze / ccgdesign / ccgbuild / ccgdebug / ccgoptimize / ccgreview / ccgtest) and the verify- quality gates. Use when a task is a whole feature, a refactor, a bug whose cause is not yet known, or any change large enough that one straight-through…
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
flow-next-features
Seed or maintain the committed user-POV drive map at .flow/features/ so QA and drive reuse how a user reaches each feature.
flow-next-qa
Live-app QA pass derived from the spec. Drives the running app, files P0/P1/P2 findings with evidence, emits a YES or NO qaverdict receipt.