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 oaslananka/zaptrace --skill zaptrace-proof-pack-reviewgit clone --depth 1 https://github.com/oaslananka/zaptraceWrote 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/oaslananka/zaptrace/zaptrace-proof-pack-review)<a href="https://agentmods.dev/skills/oaslananka/zaptrace/zaptrace-proof-pack-review"><img src="https://agentmods.dev/badge/skills/oaslananka/zaptrace/zaptrace-proof-pack-review/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/oaslananka/zaptrace/zaptrace-proof-pack-review"><img src="https://agentmods.dev/badge/skills/oaslananka/zaptrace/zaptrace-proof-pack-review.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00545 |
| Opus 5 | $0.00015 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00055 |
Grade A, and why
zaptrace-proof-pack-review 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZapTrace Proof-Pack Review
Use this skill when the user asks to create, inspect, compare, or explain ZapTrace proof-pack evidence for a local design.
When to use
Use this skill for:
- Listing available proof checks
- Running bounded proof checks for a parsed design
- Reviewing proof artifacts, hashes, assumptions, skips, and gate outcomes
- Comparing proof evidence across revisions
- Preparing a human-review handoff
Do not use a passing proof pack as a fabrication, safety, compliance, or production-readiness guarantee.
Required inputs
Collect:
- Parsed design identity or local design file
- Proof-pack directory or requested output directory
- Required checks and policy context
- Source revision and environment identity when reproducibility matters
- Known assumptions and approved skips
MCP and CLI workflow
- Use
proof_list_checksto discover the available checks. - Parse and inspect the design with
design_parse_fileanddesign_inspectwhen no design identity exists. - Run
proof_run_designfor a design-bound proof result, orproof_runfor the supported proof workflow. - Inspect related lifecycle records with
audit_list_eventswhen decisions or mutations must be traced. - Verify that reported artifacts carry stable hashes or evidence identities and that the source revision is recorded when available.
- Keep failed, skipped, unsupported, degraded, and human-review-required results distinct from passing results.
- For command-line reproduction, use the documented
zaptrace proofcommands from the source checkout and retain the machine-readable report.
Quality checks
The review must verify:
- Design or source revision identity
- Check inventory and policy identity
- Artifact hashes and referenced files
- Assumptions, warnings, skips, and unsupported domains
- Automated gate result
- Human-review or fabrication-review status as a separate field
- Reproduction command or environment notes when requested
Failure modes
Stop and report clearly when:
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 · 77 lines · 29 tokens per session scan A 0974dbccc59a
zaptrace-proof-pack-review is a skill published in the GitHub repository oaslananka/zaptrace (0 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 545 once invoked, about $0.0001 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
kicad
Use when designing electronic circuits and PCBs — schematic capture, PCB layout, 3D viewer, SPICE simulation, Gerber export. KiCad: the leading open-source EDA/PCB design suite.
multisim-verify-requirements
A review method that turns circuit design requirements into measurable tests and checks them against Multisim experiment data. It reports each requirement as passed, failed, or not yet verified.
altium-schematic-review
Review an Altium schematic (.SchDoc) — find unconnected pins, missing footprint links and net errors, then judge each candidate against the datasheet before calling it a defect. Triggers: "review this schematic", "check my circuit", "ERC", "floating pins", "unconnected", "any missing footprints", "does this schematic…
pcb-design
Design, modify, review, validate, or export a KiCad schematic or PCB from natural-language hardware requirements. Use for circuit design, component selection, schematic capture, footprint assignment, board layout, routing, ERC/DRC, BOM, Gerbers, and manufacturing handoff through the KiCad MCP tools.
kicad-library
Library management workflow for KiCAD — creating symbols, footprints, and managing libraries via MCP tools. Triggers on: "create a symbol", "make a footprint", "custom component", "register library", "find a part", "pin numbering", "new symbol", "new footprint", "add to library", "library path", "pad layout".
kicad-pcb
Workflow skill for KiCAD PCB layout and routing via MCP tools. Triggers on: "layout the board", "route traces", "PCB", "place footprints", "copper pour", "board outline", "differential pair", "board setup", "track width", "via", "zone", "design rules", "stackup", "silkscreen".