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/darellchua2/opencode-config-template/coverage-readme-workflow-skillnpx skills add darellchua2/opencode-config-template --skill coverage-readme-workflow-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/coverage-readme-workflow-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/coverage-readme-workflow-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/coverage-readme-workflow-skill.svg" alt="Measured on agentmods" 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.00026 | $0.04929 |
| Opus 5 | $0.00013 | $0.02465 |
| Sonnet 5 | $0.00005 | $0.00986 |
| Haiku 4.5 | $0.00003 | $0.00493 |
Grade C, and why
coverage-readme-workflow-skill scanned grade C with 1 finding 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
9. **Iteration safety**: bounded-by-default (`Iterations: 25`); safety blocks `.env`, `node_modules/`, `rm -rf`, `git push --force`. See `autoresearch-core-skill/references/iteration-safety.md`. How it starts
The opening of the file, as written. The whole thing — 647 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I implement a complete test coverage documentation workflow that ensures coverage percentages are displayed in README.md files:
- Detect Project Type: Identify whether the project is Next.js (JavaScript/TypeScript) or Python
- Run Tests with Coverage: Execute test suite with coverage collection for the detected framework
- Parse Coverage Output: Extract coverage percentage from test output (lines, statements, branches, functions)
- Generate Coverage Badge: Create or update coverage badge in industry-standard format (Shields.io badge)
- Update README.md: Add or update coverage badge and percentage display in README.md following industry best practices
- Handle Edge Cases: Deal with missing coverage configuration, zero coverage, or coverage threshold violations
When to use me
Use this workflow when:
- You're creating a new Next.js application or Python project
- You've just added tests to an existing project
- You want to ensure test coverage is visible in project documentation
- You're following industry standard practices for displaying code quality metrics
- You need to update coverage percentage after adding new features
- You're preparing for a code review or PR submission
- You want to track coverage trends over time
Integration: This skill is typically used alongside:
test-generator-framework: After generating testsnextjs-unit-test-creator: After generating Next.js testspython-pytest-creator: After generating Python testsnextjs-pr-workflow: Before creating a PRpr-creation-workflow: Before creating a PR
Prerequisites
- Next.js project with
package.jsonOR Python project withpyproject.toml/requirements.txt - Test framework installed (Jest/Vitest for Next.js, pytest for Python)
- Coverage tools available (built-in to Jest/Vitest, pytest-cov for pytest)
- README.md file exists in project root
- Write permissions to update README.md
- Tests must pass before coverage display
Note: If coverage tools are not installed, this skill will guide you through installation.
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.
- 3d ago First seen · 647 lines · 26 tokens per session scan C 256087c53500
coverage-readme-workflow-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed today), licensed Apache-2.0. It adds 26 tokens to every session and 4,929 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
pr-verify
Verify a Docglow change actually works before submitting or merging a PR. Runs the conformance suite, then a behavioral verification pass (flag matrix, artifact-join spot checks, pipeline contract sweep, payload budget). Use when reviewing a PR, self-reviewing a branch before opening a PR, or when asked to "verify…
qa
Risk-scored quality assessment of an increment via specweave qa. Use when saying "qa", "quality check", "risk assessment", or before deciding whether an increment is ready to close.