crypto-audit-router
Top-level orchestrator for the crypto audit framework.
When to Use
- Starting a new audit and deciding the execution order
- Choosing between
ecc-pairing-auditor, zk-circuit-auditor, dkg-threshold-auditor, rust-crypto-safety, or spec-delta-checker
- Moving a suspected issue from domain review to verification, reporting, and indexing
- Coordinating multi-skill audits without losing handoff artifacts
When NOT to Use
- Replacing the domain auditors themselves
- Writing final findings without
crypto-fp-check
- Querying or writing prior art directly without deciding whether the finding is verified and citable
Rationalizations to Reject
| Rationalization |
Why it is wrong |
| "No ZK code, skip zk-circuit-auditor" |
Fiat-Shamir transcripts appear outside ZK circuits too |
| "It's just Rust safety, no crypto-specific review needed" |
rust-crypto-safety covers timing, zeroize, and unsafe, which are crypto-specific |
| "We already ran spec-delta-checker, skip domain audit" |
spec-delta-checker finds drift; domain auditors find implementation bugs unrelated to the spec |
| "It runs on SP1, so zkvm-auditor covers it" |
zkvm-auditor covers the runtime; the application's prover inputs, witnesses, and settlement contract need proven-state-transition-auditor |
| "The settlement contract is plain Solidity, out of scope" |
The contract is the proof consumer and holds every liveness guarantee; it is in scope through proven-state-transition-auditor |
Workflow
- Load machine-readable route metadata from
../../../_meta/router-matrix.yaml
- Load machine-readable skill trigger metadata from
../../../_meta/codex-skill-registry.yaml
- Read
references/routing-matrix.md as the human-readable mirror of registry policy
- Execute
workflows/full-audit-flow.md to keep the end-to-end sequence consistent
- Preserve the output contract from each skill before routing to the next one
Routing Authority
- Auto-routing eligibility is determined by
trigger_mode in
../../../_meta/codex-skill-registry.yaml.
trigger_mode: router_auto skills are eligible when predicates match.
trigger_mode: user_triggered_only skills must never be auto-selected.
agents/openai.yaml provides UI/discovery metadata only and does not override
routing policy.
Session State Enforcement
- Every handoff must preserve schema validity against
zk-findings/sessions/session-state-schema.json.
- Use
references/state-machine.md to enforce legal phase transitions and
mutation boundaries (open_findings -> verified_findings, next_steps
refresh, closeout checks).
- If any required session-state field is missing, route back to the earliest
phase that can repair the state before progressing.
Routing Scope
This router is responsible for sequencing crypto-audit-context,
spec-delta-checker, the domain auditors, crypto-fp-check,
crypto-report-writer, and zkbugs-index.
Output Contract
Produce an audit routing plan that includes:
- The chosen skill sequence and why each skill was selected
- The current artifact handed from one phase to the next
- The stop condition for each phase
- The next unresolved branch or escalation point
Reference Index
- references/routing-matrix.md
- references/state-machine.md
- workflows/full-audit-flow.md
1---2name: crypto-audit-router-23description: >4 Route a full cryptographic or ZK audit across the framework. Use when you5 need to decide which skill should run next, which domain auditors apply, or6 how to move from initial context to verified finding, report, and index flow.7allowed-tools:8 - Read9 - Grep10 - Glob11metadata:12 source: https://skillmd.com/skills/yue-zhou1/crypto-audit-router-213---1415# crypto-audit-router1617Top-level orchestrator for the crypto audit framework.1819## When to Use2021- Starting a new audit and deciding the execution order22- Choosing between `ecc-pairing-auditor`, `zk-circuit-auditor`, `dkg-threshold-auditor`, `rust-crypto-safety`, or `spec-delta-checker`23- Moving a suspected issue from domain review to verification, reporting, and indexing24- Coordinating multi-skill audits without losing handoff artifacts2526## When NOT to Use2728- Replacing the domain auditors themselves29- Writing final findings without `crypto-fp-check`30- Querying or writing prior art directly without deciding whether the finding is verified and citable3132## Rationalizations to Reject3334| Rationalization | Why it is wrong |35|---|---|36| "No ZK code, skip zk-circuit-auditor" | Fiat-Shamir transcripts appear outside ZK circuits too |37| "It's just Rust safety, no crypto-specific review needed" | `rust-crypto-safety` covers timing, zeroize, and `unsafe`, which are crypto-specific |38| "We already ran spec-delta-checker, skip domain audit" | `spec-delta-checker` finds drift; domain auditors find implementation bugs unrelated to the spec |39| "It runs on SP1, so zkvm-auditor covers it" | `zkvm-auditor` covers the runtime; the application's prover inputs, witnesses, and settlement contract need `proven-state-transition-auditor` |40| "The settlement contract is plain Solidity, out of scope" | The contract is the proof consumer and holds every liveness guarantee; it is in scope through `proven-state-transition-auditor` |4142## Workflow4344- Load machine-readable route metadata from `../../../_meta/router-matrix.yaml`45- Load machine-readable skill trigger metadata from `../../../_meta/codex-skill-registry.yaml`46- Read `references/routing-matrix.md` as the human-readable mirror of registry policy47- Execute `workflows/full-audit-flow.md` to keep the end-to-end sequence consistent48- Preserve the output contract from each skill before routing to the next one4950## Routing Authority5152- Auto-routing eligibility is determined by `trigger_mode` in53 `../../../_meta/codex-skill-registry.yaml`.54- `trigger_mode: router_auto` skills are eligible when predicates match.55- `trigger_mode: user_triggered_only` skills must never be auto-selected.56- `agents/openai.yaml` provides UI/discovery metadata only and does not override57 routing policy.5859## Session State Enforcement6061- Every handoff must preserve schema validity against62 `zk-findings/sessions/session-state-schema.json`.63- Use `references/state-machine.md` to enforce legal phase transitions and64 mutation boundaries (`open_findings` -> `verified_findings`, `next_steps`65 refresh, closeout checks).66- If any required session-state field is missing, route back to the earliest67 phase that can repair the state before progressing.6869## Routing Scope7071This router is responsible for sequencing `crypto-audit-context`,72`spec-delta-checker`, the domain auditors, `crypto-fp-check`,73`crypto-report-writer`, and `zkbugs-index`.7475## Output Contract7677Produce an audit routing plan that includes:7879- The chosen skill sequence and why each skill was selected80- The current artifact handed from one phase to the next81- The stop condition for each phase82- The next unresolved branch or escalation point8384## Reference Index8586- [references/routing-matrix.md](references/routing-matrix.md)87- [references/state-machine.md](references/state-machine.md)88- [workflows/full-audit-flow.md](workflows/full-audit-flow.md)