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-testsgit 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-tests)<a href="https://agentmods.dev/skills/dodobrands/peekie/peekie-tests"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-tests/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-tests"><img src="https://agentmods.dev/badge/skills/dodobrands/peekie/peekie-tests.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.00000 | $0.01735 |
| Opus 5 | $0.00000 | $0.00868 |
| Sonnet 5 | $0.00000 | $0.00347 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
peekie-tests 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 11d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
peekie tests
Parse a .xcresult bundle and emit per-module test results with fully-qualified test names, durations, and failure messages.
Synopsis
peekie tests <xcresult-path> [flags]
Flags
| Flag | Default | Notes |
|---|---|---|
<xcresult-path> |
— | Required positional. Path to the .xcresult bundle. |
--format json|list|sonar |
list |
Output format. Default differs from sister subcommands — tests defaults to list, others default to json. |
--include <statuses> |
all 6 (success,failure,expectedFailure,skipped,mixed,unknown) |
Comma-separated list. Filters which tests appear in output. Status names are case-sensitive. |
--include-device-details true|false |
false |
When true, device names appear in qualifiedName (e.g. … / testFoo() [iPhone 15 Pro]). Useful for matrix runs. |
--tests-path <path> |
— | Required with --format sonar. Source-tree path used for file/line correlation in the SonarQube report. Ignored for json / list. |
--attachments skip|export |
skip |
When export, each test JSON gains an attachments array AND files are extracted to disk. |
--attachments-to <dir> |
— | Required with --attachments export. Directory where attachment files are written. |
-v, --verbose |
false |
Debug-level logging to stderr. |
Output shape
--format json (default-flat structure)
Per-module tests array with fully-qualified names. Root-level @Test functions (no enclosing @Suite), nested @Suite types, and backtick-escaped names all appear flat in this array.
{
"modules": [
{
"name": "ExamplesTests",
"files": [],
"tests": [
{"qualifiedName": "ExamplesTests / 2 + 3 = 5", "status": "success", "durationMs": 11.99},
{"qualifiedName": "ExamplesTests / ExampleSUITests / failure()", "status": "failure", "durationMs": 8.34, "message": "Expected 5.0 but got 6.0"},
{"qualifiedName": "ExamplesTests / OuterSuite / InnerSuite / DeeplyNestedSuite / deeplyNestedSuccess()", "status": "success", "durationMs": 1.2}
]
}
]
}
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.
- 11d ago First seen · 157 lines · 0 tokens per session scan A ddf0401bd0d2
peekie-tests is a skill published in the GitHub repository dodobrands/Peekie (32 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,735 tokens. 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…
Bun Test Runner
Fast test execution with Bun's built-in test runner including snapshot testing, mocking, code coverage, lifecycle hooks, DOM testing with happy-dom, and migration from Jest and Vitest to Bun test.
roundtrip-radar
Per-journey code audit tracing data through complete user flows for bugs, data safety, performance, and round-trip completeness. Discovers workflows, audits each end-to-end, rolls up cross-cutting issues, and supports natural-language flow tracing. Triggers: "roundtrip audit", "trace user journey", "/roundtrip-radar".
verify
Drive CrowTelemetry's OTLP ingest end-to-end — boot the real receiver, POST OTLP JSON with curl, inspect the SQLite db.
redbar.fix
Write the missing tests for the gaps redbar found, following the canonical standard for that layer (Playwright's best practices for e2e, Vitest/Jest idiom for unit, Testcontainers for integration). Reads .redbar/gaps.json, writes one test file per gap, RUNS each test it wrote, and never leaves a failing test behind …