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 skills add dodobrands/Peekie --skill peekie-coveragegit clone --depth 1 https://github.com/dodobrands/PeekieWrote 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/dodobrands/peekie/peekie-coverage)<a href="https://agentmods.dev/skills/dodobrands/peekie/peekie-coverage"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-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/dodobrands/peekie/peekie-coverage"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-coverage.svg" alt="Reviewed on agentmods" width="80" 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.00115 | $0.01177 |
| Opus 5.5 | $0.00046 | $0.00471 |
| Sonnet 5.5 | $0.00023 | $0.00235 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
peekie-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 1mo 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
peekie coverage
Emit code coverage from a .xcresult bundle as a hierarchical JSON structure (or list).
Synopsis
peekie coverage <xcresult-path> [flags]
Flags
| Flag | Default | Notes |
|---|---|---|
<xcresult-path> |
— | Required positional. Path to the .xcresult bundle. |
--format json|list |
json |
Output format. |
-v, --verbose |
false |
Debug-level logging to stderr. |
There is no --include flag on peekie coverage. Filter modules/files with jq.
Output shape
--format json (default)
{
"coverage": 0.6234,
"modules": [
{
"name": "Calculator",
"coverage": 0.71,
"coveredLines": 167,
"totalLines": 233,
"files": [
{"name": "Calculator.swift", "path": "/.../Calculator.swift", "coverage": 0.71, "coveredLines": 167, "totalLines": 233}
]
},
{
"name": "Networking",
"coverage": 0.42,
"coveredLines": 84,
"totalLines": 200,
"files": [
{"name": "Client.swift", "path": "/.../Networking/Client.swift", "coverage": 0.50, "coveredLines": 50, "totalLines": 100},
{"name": "Endpoint.swift", "path": "/.../Networking/Endpoint.swift", "coverage": 0.34, "coveredLines": 34, "totalLines": 100}
]
}
]
}
- Top-level
coverageis overall percentage as0.0–1.0(multiply by 100 for percent). - Each module and file carries
coverage,coveredLines,totalLines. pathis the absolute source-file path captured at build time.
--format list
Human-readable, indented by module → file. Good for terminal, not for piping.
Recipes
Overall coverage as a percentage integer
peekie coverage Tests.xcresult | jq '.coverage * 100 | floor'
Overall coverage with one decimal place
peekie coverage Tests.xcresult | jq '(.coverage * 1000 | floor) / 10'
(.coverage * 1000 | floor) / 10 keeps it pure jq — no bc, no printf. For two decimals, use * 10000 | floor) / 100.
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.
- 1mo ago First seen · 126 lines · 115 tokens per session scan A c6443f8148d5
peekie-coverage is a skill published in the GitHub repository dodobrands/Peekie (32 stars, last pushed yesterday), licensed Apache-2.0. It adds 115 tokens to every session and 1,177 once invoked, about $0.0005 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
swift-testing-expert
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and…
swift-testing
Expert guidance on Swift Testing best practices, patterns, and implementation. Use when developers mention: (1) Swift Testing, @Test, #expect, #require, or @Suite, (2) "use Swift Testing" or "modern testing patterns", (3) test doubles, mocks, stubs, spies, or fixtures, (4) unit tests, integration tests, or snapshot…
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…