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 agentmods add skills/affandar/duroxide/duroxide-code-coveragenpx skills add affandar/duroxide --skill duroxide-code-coveragegit clone --depth 1 https://github.com/affandar/duroxideWhat 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 | $0.00042 | $0.00697 |
| Opus 5 | $0.00021 | $0.00349 |
| Sonnet 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 2d 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.
- 2d 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 (20 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 697 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
agent-task-mapping
Map tasks to specialist agents. Use when choosing which agent for a job, comparing agent capabilities, or routing to React/Next.js/Playwright/docs/code-quality experts. Keywords: which agent, best agent for this, delegate to expert, agent capability mapping.
implement
Execute tasks from track plan with TDD workflow and git commit integration.
sql-reporting
Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
verify-security
安全校验关卡。自动扫描代码安全漏洞,检测危险模式,确保安全决策有文档记录。当用户提到安全扫描、漏洞检测、安全审计、代码安全、OWASP、注入检测、敏感信息泄露时使用。在新建模块、安全相关变更、攻防任务、重构完成时自动触发。.
development
开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.