customize

An interactive settings command for choosing how DeepInit analyzes a project and what it produces.

In plain words
What is it for?
Configuring analysis speed, issue-detection coverage, reports or SARIF output, repository scope, spending limits, and notification behavior.
Why use it?
It replaces manually typed options with selectable choices for depth, issue checks, outputs, scope, cost, and freshness notifications.

Command

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.

agentmods
npx agentmods add commands/deepfusionlabs/deep-init/customize
Clone the repo
git clone --depth 1 https://github.com/deepfusionlabs/deep-init
Per session 53 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 569 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00053 $0.00569
Opus 5 $0.00026 $0.00284
Sonnet 5 $0.00011 $0.00114
Haiku 4.5 $0.00005 $0.00057

Measured yesterday against content hash 794c7bf2a216, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

customize 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 yesterday.

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/customize.md · 21 lines

What it actually says

Run the deep-init skill in interactive customize mode (equivalent to --interactive). Load skills/deep-init/SKILL.md.

BEFORE any analysis, collect the run settings as type-safe button choices using the AskUserQuestion tool — the "Customize picker" flow in SKILL.md — so the user never hand-types a flag. Ask only the high-value questions (each Enter-skippable, keeping the max-quality default):

  1. Depth & speed — Deep (default) / Thorough / Fast
  2. Issue detection — All families (default) / Core only (IF-1…IF-5) / Off
  3. Outputs — Report (Docs+Insights) / SARIF (multi-select; both on by default)
  4. Scope — Whole repo (default) / Pick components
  5. Cost ceiling — $25 (default) / $50 / Custom
  6. Freshness & notifications — Keep defaults / Configure… / Turn the nudge off / Pause in this repo

Question 6 governs the proactive freshness surfaces (the SessionStart staleness nudge + commit breadcrumb / auto-update). Unlike 1–5 it controls future behavior, so on Configure… drill into a short follow-up AskUserQuestion (session-start nudge on/off · cadence window/session/always + window-hours [default window/24h] · decline back-off notify-snooze-hours [default 1 week] · commit breadcrumb · auto-update · install the commit hook) and — per the SKILL.md Freshness controls spec — persist the chosen freshness keys ONLY on an explicit confirmation, via the surgical schema-validating writer (python "${CLAUDE_PLUGIN_ROOT}/tools/freshness_config.py" --root <repo> --set <key>=<value> --apply; Pause in this repo writes .claude/.deepinit-no-nudge instead). This is the one narrow exception to "a run never writes .ai/deepinit.config" — never hand-edit, never write without the user's "yes".

Then resolve the effective settings (max-quality defaults ← .ai/deepinit.config ← the picker answers), echo the one-line resolved panel, and run the full pipeline. Anything the picker does not cover stays available in .ai/deepinit.config (schema-validated) or as a flag.

$ARGUMENTS

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.

  1. yesterday First seen · 21 lines · 53 tokens per session scan A 794c7bf2a216

Subscribe to this mod's changes

customize is a command published in the GitHub repository deepfusionlabs/deep-init (6 stars, last pushed 12d ago), licensed MIT. It adds 53 tokens to every session and 569 once invoked, about $0.0003 per session on Opus 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-31.