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 zkp2p/zkp2p-skills --skill peer-protocol-tracegit clone --depth 1 https://github.com/zkp2p/zkp2p-skillsWrote 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/zkp2p/zkp2p-skills/peer-protocol-trace)<a href="https://agentmods.dev/skills/zkp2p/zkp2p-skills/peer-protocol-trace"><img src="https://agentmods.dev/badge/skills/zkp2p/zkp2p-skills/peer-protocol-trace/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/zkp2p/zkp2p-skills/peer-protocol-trace"><img src="https://agentmods.dev/badge/skills/zkp2p/zkp2p-skills/peer-protocol-trace.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.00036 | $0.01005 |
| Opus 5 | $0.00018 | $0.00502 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00101 |
Grade A, and why
peer-protocol-trace 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 2d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace Peer intents, deposits, and transactions
Use this for one concrete incident or a bounded set of related deposits/intents. Establish the chain/environment and supplied identifier first. A transaction hash, intent hash, and composite deposit ID are different keys; a numeric deposit ID needs its escrow address. Do not infer identity by searching unrelated wallets.
Reconstruct the lifecycle
Use @zkp2p/[email protected] for protocol/indexer reads and @zkp2p/[email protected] for current entity types. The checked example uses the supported indexer wrappers. Configure a read-only wallet address, chain/RPC, and runtime environment; indexer credentials, if needed, remain in the host's secret store. Do not use a retired HyperIndex URL from another environment.
- If given a transaction, fetch it and its receipt from that chain. Record status, block, sender, destination contract, and decoded relevant events using the matching deployed ABI. A transaction being found or mined is not enough: check receipt success. If pending/unknown, say so before treating missing events as absence.
- Look up an intent with
client.indexer.getIntentByHash(hash)or deposit withgetDepositById(id, { includeIntents: true }). For an owner-scoped question use a boundedgetOwnerIntents/deposit query. Preserve full IDs returned by the indexer rather than rebuilding them from obsolete SDK comments. - Follow intent → escrow/deposit → owner/recipient → signal, fulfillment, cancellation/prune, and extension events. Read the actual on-chain intent via
client.getIntentwhere applicable; it can be absent after settlement/pruning, so a missing active record does not erase receipt history. - Reconcile token amount, fiat obligation, verified payment, released amount, fees, timestamps, and recipient. Money fields are integer strings/bigints with schema-defined decimals. Do not convert arbitrary monetary values through JavaScript
Number. - Compare indexed observation with confirmed receipts/live contract state. Record the latest indexed evidence/block available. If the indexer lags, retry bounded reads; a lagging null is inconclusive, not a failed transaction or permission to replay it.
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.
- 2d ago First seen · 42 lines · 36 tokens per session scan A 4fb15cc546df
peer-protocol-trace is a skill published in the GitHub repository zkp2p/zkp2p-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,005 once invoked, about $0.0002 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-09-10.
Other skills, from other repositories
code-changes
Orchestration workflow for any task that ends in code changes: issue analysis, pull request review, feature implementation, bug fixes, refactors, or fleshing out an idea. MUST be invoked at the start of such a task, before reading or writing any code. Defines how to analyze first, gate on user approval, plan, pick the…
cross-environment-semantic-drift
L1 trigger - audits L1/L2 boundary bugs, precompile context assumptions, integer width mismatches at environment boundaries, and EVM-on-non-EVM drift.
consensus-math-correctness
L1 trigger - audits consensus arithmetic for truncation, unused bounds, EMA direction, and threshold edge errors.
alchemy-cli
Use the Alchemy CLI (@alchemy/cli) for live blockchain data, transaction lookups, NFT/token/portfolio queries, simulation, tracing/debugging, contract reads/writes, wallet-signed sends, swaps and cross-chain bridges, Solana RPC/DAS plus wallet sends, webhook management, and Alchemy app administration. Preferred…
finish-it
Get a stalled or sprawling game project to ship: diagnose the death loop, cut to the core, set a binary finish line.
skmtc-debug
Diagnose failures in SKMTC sessions — no output, wrong output, error messages, bundle freshness, parseIssues, "Registered definition mismatch", ref cycles, "Module not found" in generated code, or any other broken behavior. Applies across both CLI usage and generator authoring contexts. Use this skill when the user…