One narrow agent audit workflow, packaged so it can be reused.
This is for teams already using Codex, Claude Code, Cursor, Copilot, or an MCP/tool-call workflow and wanting the run to leave clearer evidence than "done" or "looks good."
Options
One audit workflow pack
$99
I turn one narrow repeated workflow into reusable instructions, a receipt template, and verification notes.
Setup + revision
$299
Same pack, plus setup guidance and one revision after you test the workflow in your repo or toolchain.
Deliverable
AGENTS.md or repo-instruction patch skills//SKILL.md templates/ .md or .json verification.md README.md with run and review instructions
Sample $99 deliverable
Example scope: turn a repeated PR review request into an audit workflow that can honestly say which files were inspected, which checks ran, and what remains unverified.
pr-review-audit-pack/ AGENTS.md patch skills/pr-review-audit/SKILL.md skills/pr-review-audit/verification.md templates/pr-review-receipt.json README.md receipt fields: files_reviewed checks_run checks_skipped evidence_gaps verdict: pass | fail | incomplete
What to send
- the repeated workflow you want packaged, in one or two sentences
- the current prompt, SOP, checklist, issue template, log, or example run
- who reviews the final receipt: you, a maintainer, a client, or an internal team
- the one result that would make the pack useful on the next real run
Public validation example
In a Traceary sensitive-file audit issue, the maintainer accepted the same receipt-shaped split: sensitive-path match, access operation, redaction state, audit coverage, and coverage gaps. This is public validation of the field model, not a customer claim.
Good fit
- PR/code review where "no issues found" needs evidence
- MCP/tool-call audit log where identity, policy, or coverage can be incomplete
- safe-edit or sensitive-file workflow where skipped checks must be visible
- large agent audit reports that need coverage and verifier counts preserved
Bad fit
- full app builds
- generic prompt packs with no verification boundary
- growth hacks, spam, scraping, platform evasion, or credential misuse
- one-off tasks nobody will run again
Payment and delivery
- Open the paid-pilot request with the workflow, current material, and success condition.
- I reply with a fit/not-fit judgment and exact deliverable scope before taking payment.
- If the scope fits, payment is collected before delivery by invoice or an agreed payment link.
- The delivered pack includes reusable instructions, a receipt template, verification notes, and one completed example receipt for your workflow.
Start
Open a free fit-check issue first and choose the paid-pilot interest option. I will say whether it is worth paying for before taking the work.