docs: put the guided command first, and a prompt for people who use an AI - #36
Merged
Conversation
…n AI The site explained the threat and documented fourteen commands. Someone who has just found infected repositories does not want fourteen commands; they want to be told what to do next. infected.html now opens with 'snare respond' before the manual sequence, and says plainly what it will and will not do: it revokes what it safely can, opens the browser where it cannot, asks before every push, defaults everything that writes to no, and asks the purge-history question once rather than per repository. It also says it will not pretend to have rotated your credentials for you — a step that blocks you is a step you abandon. The hand-driven sequence stays below for anyone who would rather drive. install.html gains a copy-paste prompt for Claude Code, Cursor, Copilot or anything else that can run commands. It installs snare, runs selftest before trusting any result, checks the machine, and scans — and it explicitly forbids the assistant from running fix, --push or --purge-history without asking first, because those rewrite history. It also tells the assistant the two things people get wrong: rotate before cleaning, and "guard scan: clean" does not mean you were never infected. commands.html gains a "Start here" section, since the reference is where people look a command up. Content only. No layout, CSS or build changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The site explained the threat and documented fourteen commands. Someone who has just found infected repos doesn't want fourteen commands — they want to be told what to do next.
infected.htmlnow opens withsnare respondbefore the manual sequence, and says plainly what it will and won't do: revokes what it safely can, opens the browser where it can't, asks before every push, defaults everything that writes to no, asks the purge question once. And that it won't pretend to have rotated your credentials for you — a step that blocks you is a step you abandon. The hand-driven sequence stays below.install.htmlgains a copy-paste prompt for Claude Code / Cursor / Copilot. It installs snare, runsselftestbefore trusting any result, checks the machine, and scans — and explicitly forbids the assistant from runningfix,--pushor--purge-historywithout asking, since those rewrite history. It also tells the assistant the two things people get wrong: rotate before cleaning, andguard scan: clean≠ never infected.commands.htmlgains a "Start here" section.Content only — no layout, CSS or build changes. All 9 pages: balanced tags, 0 parse errors.