[feat] Add a command reference table to AGENT-INSTALL.md - #162
Merged
Conversation
Add a scannable per-command reference near the top of AGENT-INSTALL.md covering all 12 CLI commands, each with: what it does, whether it reads source, what it writes, and what it sends over the network. Summarizes the existing prose (left intact below) so an agent gets full per-command context at a glance. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Comprehensive command reference table enhances clarity without altering code behavior. 🎯 Quality: 96% Elite · 📦 Size: Small 📈 This month: Your 67th PR — above team average · Averaging Excellent |
Contributor
Author
|
/review |
daniloradovic
approved these changes
Aug 21, 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
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.
What
Adds a Command reference table near the top of
AGENT-INSTALL.md— all 12 CLI commands at a glance, each with four fixed, agent-parseable fields: what it does, reads your source?, writes to your project, sends over the network.Why
The agent-facing install reference documented each command in dense prose bullets. This surfaces the per-command facts that drive agent trust (does it read my source? what does it send?) in a scannable form, and makes "what each command does and doesn't do" explicit — e.g.
protectruns only viasetup;mapis never run by another command. That directly counters the documented refusal mode where agents attributeprotect's blast radius toscan/guide.Scope / safety
MAINTAINING.mdguardrails: no reassurance language, no broadened privacy claims, and it strengthens capability disclosure (all 12 commands listed up front).pack-safetychecks the filename), so the suite is unaffected.Gate (before release)
AGENT-INSTALL.mdis a gated artifact. The field-test gate —node field-test/run.mjs --persona hostile --rounds 3— installs the published package, so it can only exercise this change after publish. Run it at/after release.