Hi Eros!
Good instinct that these aren’t coming from your account, but they’re also not orphaned or legacy rules. The blocks you’re seeing (committing-changes-with-git, creating-pull-requests, plus the communication, code-writing, and “real environment” ones) are Composer 2.5’s built-in session instructions. They’re baked into the model’s prompt, not stored as rules on disk, in Settings, in Memories, or synced to your account.
That answers your three questions directly:
- Where they live: in Composer 2.5’s built-in prompt, not on your account. There’s nothing account-side for you (or us) to point to or clear.
- How to “remove” them: you can’t delete them individually, and there’s nothing to clear server-side. Switching to a non-Composer model (Opus, Sonnet, GPT) drops this specific set. Those models just carry their own built-ins instead.
- No downgrade or state.vscdb wipe needed, and I’d avoid wiping state.vscdb regardless since it holds your chat history.
On the token math: these built-ins are a small, fixed cost. The levers that actually move your first-load token count are always-applied project/user rules, skills, MCP prompts, and long chat history, so trimming those will help more than chasing the built-ins.
Same finding was confirmed here if you want the extra context: Composer 2.5 always on injected rules.