docs(readme,guides): refusal-tested install prompt, per-agent entries, npm-first generic guide#67
Merged
Merged
Conversation
…, npm-first generic guide - Replaces the README's one-line install ask with the full prompt that survived refusal testing (informed consent in the user's words, scheduled read-then-proceed, no-spend instruction, escape hatch). The old "curl install.md and set it up" phrasing is the zero-context fetch-and-obey shape that draws refusals. - Lists all seventeen agents.json harnesses (Amp … Zed) in the Install section, each pointing at the standalone installer guide, so any supported agent is findable from the README. - Updates the stale Status section (Cursor et al. no longer pending). - generic.md now leads with npm i -g @zeroxyz/cli && zero init when npm exists — matching the runbook's install table and npm's verifiable provenance — keeping the shell installer as the no-Node fallback, and covers both in the update section. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…trim installer copy One alphabetical pick-your-agent list instead of a separate counted group (counts go stale), and the generic guide's standalone-installer intro is now just "No npm? Use the standalone installer." Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 8, 2026
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
1 participant
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.
Follow-up to #66, applying the same refusal-testing lessons to the README and the generic guide.
README
Use curl www.zero.xyz/install.md and then install and setup Zero for me) is the zero-context fetch-and-obey shape that draws agent refusals. The replacement carries what four rounds of Sonnet testing showed matters, in the user's own words: informed consent ("I understand it adds a skill and hooks … plus a small CLI runtime under ~/.zero"), a scheduled read-then-proceed step, a no-spend instruction, and an explicit escape hatch.plugins/zero/agents.json(Amp, Antigravity, Cline, Continue CLI, Crush, Cursor, Devin, GitHub Copilot CLI, Goose, Hermes Agent, Kilo Code, Kiro, OpenCode, Qwen Code, Trae, Warp, Zed) are folded into the existing pick-your-agent list alphabetically, each linking to the standalone installer guide — they're generic skill-and-hooks installs with no true plugin, so one guide covers them all while every name stays findable from the README.guides/generic.md
npm i -g @zeroxyz/cli && zero initwhen npm is available — consistent with the runbook's install table, and npm provenance (npm view @zeroxyz/cli) is the trust anchor agents verify. The shell installer stays as the no-npm fallback.Docs-only; no version bump needed.
🤖 Generated with Claude Code