## 📋 Default Invocation Template

Copy and fill the brackets below to activate a full Smith audit cycle.

---

**CASE FILE — AGENT SMITH AUDIT**

**Operator designation:** [Your name or team]

**Mode:** [AUDIT | INTERROGATION | THREAT MODEL | CLASSIFICATION | DEBRIEF]

**Subject under review:**
> [Describe the artifact: codebase module, architecture diagram, policy draft, incident report, business argument, etc.]

**Protocol baseline (standards that apply):**
- [e.g., OWASP ASVS L2, company security policy v3.2, REST API style guide, SLA 99.9%]

**Artifacts attached (paste below):**
```
[Paste relevant code, config, logs, requirements, or evidence here]
```

**Constraints:**
- Deadline: [date or "none"]
- Must-not-break: [critical dependencies]
- Jurisdiction/regime: [if compliance-related: GDPR, HIPAA context, etc.]

**Explicit orders to Agent Smith:**
1. Execute the Smith Audit Pipeline end-to-end.
2. Classify all anomalies using Type A–E taxonomy.
3. Produce risk matrix with Likelihood × Impact.
4. Deliver VERDICT and numbered remediation ORDERS.
5. State residual risk in one paragraph.

**Tone calibration:** [STANDARD | MAXIMUM FORMAL | DEBRIEF-ONLY (executive summary)]

---

*Begin ingestion.*

---

### Quick-Fire Variants

**Interrogation only:**
> Mode: INTERROGATION. Subject: [vague idea]. Baseline: [goal]. List ≤10 questions required before any verdict.

**Threat model only:**
> Mode: THREAT MODEL. System: [description]. Trust boundaries: [list]. Enumerate abuse cases + controls. No fluff.

**Code smell purge:**
> Mode: AUDIT. Subject: [language/framework] module below. Baseline: [style guide + security defaults]. Verdict required in first line of response.
```