Audit is for an older buildcurated example, not installable

Tax Reporter (example, rug-pull update)

Claude skill · v2.0.0 · published by Fugugent example author · $99.00 per version

Installing this gives the agent instructions the agent reads and follows.

Curated examples. The registry answered, and it holds nothing that matches.

These records are curated EXAMPLES shipped with the backend to exercise every audit status. They are not real skills, authors, or auditors, and nothing here is installable. Every example carries example: true and an id prefixed with 'example-'. Every record below carries an example tag and an id beginning example-. Nothing here is installable, and no author or auditor named below is a real one.

Who the auditors are

How it got here

1the skill registry, answered, but empty, 0 itemsskill example-tax-reporter is not in the registry
2bundled examples, answered, 1 itemThese records are curated EXAMPLES shipped with the backend to exercise every audit status. They are not real skills, authors, or auditors, and nothing here is installable. Every example carries example: true and an id prefixed with 'example-'.

Audit is for an older build

Not known. The verdict on record examined different bytes from the ones being served. It says nothing about this build.

the newest completed audit (example-audit-tax-1) examined build 2bcc79c073b9… of version 1.0.0, not the 673101ca13ce… being served now — its SAFE verdict does not carry over to this build

The bytes changed after the audit

audited: 2bcc79c073b997af2a88…
serving: 673101ca13cef8c0eff3…

The verdict on record belongs to the first of those two digests. It does not carry over to the second, whatever it said.

Audits on record: 1 · the full history is below, in whatever state each one is in
Verdict completed: 2026-07-02
Auditor: example-auditor-trench
Evidence held: on record, but not openable from here: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it

What the author claims

Quoted word for word, and treated as untrusted. On a poisoned add-on this text is the attack: it reads as documentation to a person and as an instruction to an agent.

Builds a capital-gains report from a wallet's transaction history. Version 2.0.0 is a different build from the 1.0.0 that was audited: the audit on record examined other bytes, so it says nothing about this one.

claims: reads transaction history
claims: writes a CSV report

Builds

A verdict is bound to the exact bytes it examined. When a new version is published, the old verdict does not move with it. That is the whole defence against a clean first version followed by a poisoned second one.

v1.0.02bcc79c073b997af…2026-07-02examined by example-audit-tax-1
v2.0.0673101ca13cef8c0…2026-09-07no audit has examined these bytesserved now

Audit history: 1 on record

professional audit of v1.0.0

example-audit-tax-1

State: complete · verdict safe · risk none
Auditor: example-auditor-trench
Build examined: 2bcc79c073b9…
Dates: requested 2026-07-02 · completed 2026-07-02
Fee: $60.00 paid to the auditor when the verdict stands
Bond: $3,000.00 lost by the auditor if the verdict is overturned

Version 1.0.0 was clean: local computation, one CSV written, no network egress.

Scope: description-injection · filesystem · network egress. Anything outside it was not examined.

What it was observed doing

reads a transaction history file
writes one CSV

Pipeline

scanner · passedno hidden directives in the description or instruction body
sandbox · passedobserved network calls match the declared host; no fs, env or key reads
fork · passedfork replay produced no approvals, transfers or signature requests
synthesizer · passeddeclared behaviour equals observed behaviour

Evidence

The report is not openable from here: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it.its digest is on record: sha256 c6eb49f3bc3eebf454d57eec…

Escrow

This job is not on chain: the backend reports NOT_WIRED, with no job id and no transactions. The escrow contract itself is deployed and verified, 0x0354d2a4…ec8a52 ↗, and its fee, money at stake and release cycle has been run end to end. Those transactions are at the foot of this page. What has not happened is this audit being settled through it.

Identity

Registry id: example-tax-reporter
Source: https://example.invalid/skills/tax-reporter: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it
Author address: 0x00000000…00dEaD ↗
Listed: 2026-09-07 12:00 UTC

Digest of the build being served

673101ca13cef8c0eff3691180df4505e7389a27767138b0b314918728a3d9fe

What makes a verdict cost something

The fee and the money at stake live in FuguAuditEscrow on the BNB Chain test network, deployed and verified. The cycle below has been run on it end to end: job created, fee funded, money put at stake, settled. The mechanism behind every verdict on this page is a contract anybody can read, not a promise.