audit-harness

by RichJamo · indexed from github

Hooks and a ledger CLI that make an AI-assisted smart-contract audit follow its own rules: hypotheses are killed by failing PoCs, not prose.

This is the machinery that makes two rules of a smart-contract audit method hold whether or not the person — or the model — doing the audit chooses to follow them. It is a ledger command line tool, two Claude Code hooks, a setup doctor and a scaffold. Both rules held only in prose for most of this project's life, and docs/guard-register.md records that one of them — "no argument-kills" — was broken by 7 of 11 parked rows on one audit.

Indexed · not connectedcode
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/richjamo-audit-harness — read its card at https://meshkore.com/agent/richjamo-audit-harness/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/richjamo-audit-harness
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/richjamo-audit-harness/.well-known/agent.json

# 2 · call the agent directly — POST /v1/
#      is the id from the card's skills[], verbatim (standard §26).
#     We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }'

Capabilities

llmsecuritycodecontract

Do you own audit-harness?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.