What is auditor:intake?

An interactive intake command for recording the scope and technical details of a blockchain security audit.

It helps capture the code version, languages, frameworks, protocol type, compliance needs, and other audit assumptions, either through questions or defaults.

It turns answers that might otherwise remain only in a conversation into a saved intake document that later audit steps can use.

auditor:intake — Command for Claude Code by solanabr/auditor-skill

Install

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.

Clone the repo

git clone --depth 1 https://github.com/solanabr/auditor-skill

Made for: Claude Code.

Or install auditor, the plugin that ships this one along with the rest of its 1 skill, 15 commands, 8 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/solanabr/auditor-skill/intake/github.svg)](https://agentmods.dev/commands/solanabr/auditor-skill/intake)

Your own site

<a href="https://agentmods.dev/commands/solanabr/auditor-skill/intake"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/intake/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/solanabr/auditor-skill/intake"><img src="https://agentmods.dev/badge/commands/solanabr/auditor-skill/intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 100 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,067 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00100	$0.01067
Opus 5.5	$0.00040	$0.00427
Sonnet 5.5	$0.00020	$0.00213
Haiku 4.5	$0.00010	$0.00107

Measured 1mo ago against content hash f72934e9622a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

auditor:intake 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 1mo 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.

commands/intake.md · 43 lines

How it starts

The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.

auditor-skill — Engagement Intake / Scope

Arguments: $ARGUMENTS

Turn the passive QUESTIONS.md questionnaire into a persisted audit_<n>/intake.md. Read QUESTIONS.md first (the source questions + the "How Answers Affect the Audit" table) and templates/intake.md (the artifact you fill). This fixes the gap where intake answers lived only in conversation state — both /auditor:audit-cycle and /auditor:audit-assist read the file you write here.

Mode

Interactive (default) — walk the human through the questions. Ask sharp, answerable questions; do not dump all 45 at once. Group by section, skip questions the repo already answers (detected language, framework), confirm rather than re-ask.
--auto — no human present (the audit-cycle path). Apply the QUESTIONS.md default for every unanswered question and record each under Assumed Defaults (Unanswered) with the exact default applied. Never leave a field blank; never assume silently.

Steps

Discover. Enumerate the repo (extensions, Anchor.toml / Cargo.toml / package.json / .github/). Pre-fill languages, framework, monorepo shape, and DEX/oracle/CPI hints from what the code shows — do not ask what the code already answers.
Pin the commit. git rev-parse HEAD. Record the full 40-char SHA and branch so the report names exactly what was reviewed.
Warm from prior audits (if available). If tools/auditor-tools is built, audit-mem warm <program-id> injects the prior protocol profile and open false-positive rulings — pre-fill from it and confirm rather than re-ask. If absent, skip.
Walk QUESTIONS.md → intake.md. Fill every section of templates/intake.md:
- Scope & commit pin — in/out of scope (honor Q44 excludes), --scope boundary.
- Languages & frameworks (Q3–Q7) — drives the scope-gated checklist set (SKILL.md → SCOPE-GATED LOADING).
- Protocol class (Q1, Q17–Q24) — gates checklist 06 + economic known-vectors when funds are handled.
- Compliance (Q35–Q38) — gates checklist 18.
- Severity calibration (Q8, Q10, Q11, Q40–Q41) — record the concrete lever applied (mainnet → +1 on fund findings; TVL > $1M → double-weight criticals; single-wallet upgrade authority → auto Severity 8+), per the QUESTIONS.md effects table. Feeds report §5.
- Trust-model inputs (critical) (Q11, Q14–Q16, Q23) — for each of admin / upgrade authority / oracle / keeper / LP / permissionless user, record who holds it, what they can do, and what the review trusts them NOT to do. "Untrusted / permissionless" is a valid, important answer. This seeds report §4.4 and §4.6, and is the actor list /auditor:threat-model expands.
- Security history (Q25–Q28).

Read the full file on GitHub · 43 lines

Changes

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.

1mo ago First seen · 43 lines · 100 tokens per session scan A f72934e9622a

Subscribe to this mod's changes

auditor:intake is a command published in the GitHub repository solanabr/auditor-skill (59 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 1,067 once invoked, about $0.0004 per session on Opus 5.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-08-30.

Security Web3 and blockchain anchor-lang audit-skill claude-skills defi-security pinnochio security-audit

auditor:intake

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

auditor-skill — Engagement Intake / Scope

Mode

Steps

What this file has done since we first saw it

Other commands, from other repositories

audit-solana

deploy

build-unity

generate-idl-client

plan-feature

profile-cu