[chaitanyagiri]

One fix, no new pages: 7 engine PRs were already open, so RUN-PM step 8 allows only the fix. This adds the tampered Claude Code extension to the security guide, which readers reach from the 31 Oct brief in #808.

What changed in security-for-ai-coding-agents

• New first section: "Were you affected by the tampered Claude Code extension?", with versions 2.1.312 and 2.1.313, the window on 29 Oct, Cursor's check command, what a "No key found" result does not prove, the cleanup steps, the Linux position, and what Cursor, Anthropic, Phorion and The Register each say.
• Description and FAQ updated, updated: 2026-10-31 added. Title and URL unchanged.
• Old copy brought up to the house rules: dashes removed, the current house line linked to the download page, and the old "agents you can actually trust" and "data that never leaves can't leak" lines removed. The guide now says prompts and code still go to the model provider unless you run a local model.

Before and after

Before (live page, 31 Oct):

After (built from this branch):

Checks

• Gate: passes with --online --no-backlink at 1,182 words, with one warning for being over the 1,150 target.
• Build: passes locally. The diff is the post, its page, the listing pages that show its description, llms.txt and the sitemap.
• Fact review: one independent review failed on 8 points, all fixed as written. I rechecked the reviewer's new quotes against Phorion and The Register. I then cut about 40 words of older copy to meet the length limit. Neither the fixes nor the cuts had a second review.

Things to know

• Fix choice: this is not the first item in refresh_queue.next. That item, is-claude-code-open-source, is a title rewrite on September numbers, and OpenSEO is signed out, so I could not check current data or measure a change. I took the security fix because it tells readers what to do about a live incident. herdr-alternatives stays queued.
• Skipped from the refresh brief: Search Console queries and the read of who ranks. The title stays as it was for that reason.
• Hero image: the old hero keeps its drawn character and orange labels, which the current scene rules would not allow in new art. This fix adds no scenes.
• Reach figure: "up to 5,000" comes only from The Register, which names no source. Cursor's notice gives no count, and the page says so.

🤖 Generated with Claude Code

[github-actions]

🚫 This PR is missing its before/after evidence

Every pull request here has to show its work. Screenshots or a short screen recording, before the change and after it.

• After — no image or video under that heading

How to fix it: edit the description, keep the ### Before and ### After headings from the template, and drag an image or video under each. GitHub uploads it inline. This check re-runs the moment you save.

A bug fix with no visible surface still needs it: show the failing behaviour, then the same steps passing. A terminal recording is fine.

Genuinely nothing to show — a CI tweak, a typo, a dependency bump? A maintainer can apply the no-visual-change label. Please don't ask unless it truly has no observable effect.

📖 CONTRIBUTING.md → Evidence is mandatory

[chaitanyagiri]

Combined into #810 at the founder's request. This PR's evidence stays here for reference.