Borrowing it
Nothing to install: this file belongs to rodydavis/signals.dart. 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/rodydavis/signals.dart/main/.agents/skills/increase-coverage/SKILL.mdgit clone --depth 1 https://github.com/rodydavis/signals.dartWrote 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/rodydavis/signals.dart/increase-coverage)<a href="https://agentmods.dev/skills/rodydavis/signals.dart/increase-coverage"><img src="https://agentmods.dev/badge/skills/rodydavis/signals.dart/increase-coverage.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00951 |
| Opus 5 | $0.00015 | $0.00476 |
| Sonnet 5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
increase-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 9d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Coverage Execution and Maximization Guide
This developer skill provides step-by-step instructions and best practices for executing code coverage tools, identifying untested paths (gaps), and writing high-fidelity unit tests to drive coverage to 100% across the monorepo.
1. Executing and Aggregating Monorepo Coverage
Our monorepo coordinates testing across multiple packages using Melos. Follow this command workflow to generate and merge coverage data:
A. Run Package Tests with Coverage
Execute the monorepo test runner. This runs flutter test --coverage (or dart test --coverage) across all packages:
melos run test
B. Combine Package Coverage Files
Run the combination script to merge individual package-level coverage/lcov.info files into a unified root lcov.info file:
melos run coverage
[!NOTE] The aggregation script (
scripts/combine_coverage.sh) dynamically rewrites path roots to be absolute and deletes temporary packagecoveragedirectories to maintain workspace hygiene.
C. Generate the HTML Coverage Report
Translate the unified lcov.info file into an interactive HTML visualization report using genhtml (part of the lcov toolkit):
genhtml lcov.info -o coverage/html
2. Pinpointing Uncovered Lines (Gap Analysis)
To quickly locate untested lines of code without browsing the entire HTML report, run the following grep and awk pipeline on the root lcov.info file:
grep -E "SF:|DA:" lcov.info | awk -F: '/SF/ {file=$2} /DA/ {split($2,a,","); if(a[2]==0) print file, a[1]}'
This output displays the absolute file path followed by the exact line number of every uncovered statement, for example:
/workspace/packages/preact_signals/lib/src/model.dart 21
/workspace/packages/preact_signals/lib/src/model.dart 25
3. Strategies for Reaching 100% Coverage
Once you identify the uncovered lines, apply these targeted testing strategies to write meaningful tests:
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.
- 9d ago First seen · 101 lines · 31 tokens per session scan A 55941b40f06a
increase-coverage is a skill published in the GitHub repository rodydavis/signals.dart (815 stars, last pushed 22d ago), licensed Apache-2.0. It adds 31 tokens to every session and 951 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
patrol-e2e-testing
Use when writing E2E/integration tests, testing native interactions like permissions or system dialogs, capturing UI regressions, or validating cross-platform behavior (Patrol 4.x).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
mocktail
Use when creating mocks, stubbing methods, verifying interactions, registering fallback values, or choosing between mocks, fakes, and real objects (Mocktail).
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
harness-engineering-lifecycle
Design, implement, and integrate generalized validation harnesses across a producer-consumer boundary after a local harness contract exists. Use when refactoring custom validation CLIs/MCPs for large polyrepos, extending Steward across sibling repos, or deploying a local tool to a consumer project for dogfooding and…