Skip to main content
This appendix is an operational checklist. For full explanations, threat model analysis, and background, see 03-3 Security, Privacy, and Supply Chain Risk. This page keeps only the criteria and the “why bother” rationale for each section.
This topic involves risks of irreversible data exfiltration and system compromise. Validate all executable configuration changes in a throwaway environment before applying them to a real workflow. Read the relevant section of 03-3 before acting; do not just tick boxes.

​
7. Scenario-specific checklists

  1. After cloning, inspect .mcp.json, .github/workflows/, .claude/, and AGENTS.md first. Unknown servers, unrecognized workflows, and unverified rules: disable them before proceeding.
  2. Running --dangerously-skip-permissions in a throwaway environment is the anti-pattern, not the recommendation: default to refusing it. Grant minimum permissions and add more only when a specific need arises.
  3. On the first run, execute all three rg scans from Section 3 and record every hit and its disposition.
  4. Confirm the account training opt-out switch before sending any data.
  5. If the run processed any untrusted content, rotate the project memory per Section 5.
Factual claims are grounded in official documentation; fast-changing items are annotated as of 2026-05.