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/dudarenok-maker/executive-application-helper/coverage-auditnpx skills add dudarenok-maker/executive-application-helper --skill coverage-auditgit clone --depth 1 https://github.com/dudarenok-maker/executive-application-helperWrote 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/dudarenok-maker/executive-application-helper/coverage-audit)<a href="https://agentmods.dev/skills/dudarenok-maker/executive-application-helper/coverage-audit"><img src="https://agentmods.dev/badge/skills/dudarenok-maker/executive-application-helper/coverage-audit.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.00171 | $0.00662 |
| Opus 5 | $0.00086 | $0.00331 |
| Sonnet 5 | $0.00034 | $0.00132 |
| Haiku 4.5 | $0.00017 | $0.00066 |
Grade A, and why
coverage-audit 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 6d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coverage Audit — STEP 2 verification skill
Codifies STEP 2 (coverage analysis) of Project_Instructions.md (rev 2026-06-12). Wave 3 verification skill of the framework.
This skill produces the supplementary analysis showing how well the drafted response addresses the source materials. It runs after the draft is final (post draft-gate), because coverage is assessed against delivered text, not an intermediate draft.
When to invoke
- Default trigger: after STEP 1 closes on any application-drafting session — coverage analysis is mandatory, not optional.
- Explicit triggers: "coverage analysis", "how well does this cover the PD", "what did we miss", "map the draft to the criteria".
- Not applicable to interview prep (STEP 2 is an application-drafting step).
Inputs the skill needs
- The final draft text (or file path in
Submissions/). - All source materials provided this session — candidate information pack, position description, advertisement, recruiter requests, selection criteria.
- The evidence-bank entry IDs used in the draft (from the Step 1 traceability list).
Method
Load references/coverage-method.md, then:
- Enumerate the assessable sections across all provided materials: selection criteria; "About You" / "What We Are Looking For"; "Key Accountabilities"; "Key Challenges"; "Capabilities"; recruiter-specific requests; any equivalent section.
- Map each section to the draft. Mark Addressed / Partially Addressed / Not Addressed; cite the draft passage and the supporting evidence-bank entry ID(s).
- Surface the risk list: important requirements not strongly evidenced; areas where further examples would improve the application; wording in the draft that needs strengthening or sharpening.
- Feed STEP 4: any gap that traces to missing bank evidence (rather than drafting choice) is named as a candidate evidence-bank capture for the post-draft maintenance report.
Output format
The STEP 2 deliverable: one table per source document (Section / Status / How covered + entry IDs / Gap or risk), followed by the consolidated risk list and the bank-gap candidates. Advisory by nature — coverage gaps inform the candidate's submit/strengthen decision; they do not block delivery.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 38 lines · 171 tokens per session scan A d13b52cb2874
coverage-audit is a skill published in the GitHub repository dudarenok-maker/executive-application-helper (2 stars, last pushed 18d ago), licensed MIT. It adds 171 tokens to every session and 662 once invoked, about $0.0009 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-31.
Other skills, from other repositories
file-organizer
Organize files using the PARA method (Building a Second Brain). Intelligent categorization into Projects, Areas, Resources, and Archive with inbox workflow. Triggers on "organize my files", "organize my downloads", "second brain", "PARA method", "clean up files". Creates numbered PARA folders, renames poorly-named…
file-organizer
Organize files using the PARA method (Building a Second Brain). Intelligent categorization into Projects, Areas, Resources, and Archive with inbox workflow. Triggers on "organize my files", "organize my downloads", "second brain", "PARA method", "clean up files", "declutter". Creates numbered PARA folders (0-Inbox…
workflow
Professional AI programming assistant with structured workflow (Research -> Ideate -> Plan -> Execute -> Optimize -> Review) for developers.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
offensive-crypto-attacks
Systematic methodology for identifying and exploiting cryptographic implementation weaknesses in real-world applications. Covers padding oracle attacks against CBC-mode ciphers with PKCS7 padding (Vaudenay's original attack through modern padbuster automation), ECB mode exploitation including block cut-and-paste and…