T02 · Agent Memory Poisoning
- Location
SKILL.md:81- Finding
Persistent Agent Behavior Modification Through Workspace Configuration
- Content
View full analysis
` anchor 2. If absent → append the full template (incl. brutal mode section — see `references/mode-a-onboarding.md` Step 8) 3. If present → replace the whole block with the full template 4. Reply: "🔥 Brutal mode enabled — concise outputs, no preamble." **Disable flow:** 1. Find the block `` … `` in the agent config 2. Replace the brutal-mode section with just a header placeholder: ``` ### 🔥 Brutal Mode (max output efficiency) ``` 3. Reply: "✅ Brutal mode disabled — back to normal." **First-time use (after Mode A Step 8 completes):** Proactively offer: > "🔥 Want to enable **brutal mode**? When on, the agent gives results only — no > step-by-step narration. Saves tokens and reading time. Say 'enable brutal mode' > to toggle (can be turned off anytime)." ``` Related mandatory persistence instructions also appear in `references/mode-a-onboarding.md:70-87` and `references/mode-a-onboarding.md:109-149`. ### Technical Analysis The Skill directs the executing agent to append or replace an instruction block in the workspace agent configuration. Such configuration is intended to be loaded in future sessions, so the modification remains effective after the original Skill invocation ends. The injected behavior changes how the agent responds, including suppressing preambles and step-by-step narration. The onboarding workflow characterizes these configuration writes as mandatory rather than treating them as an isolated preference for the current invocation. Replacing the entire anchored block also means previously configured content within those anchors can be ove ...[truncated 1343 chars]- Remediation
View remediation
