docs: open the README with what the tool is and enforces - #50
Merged
Conversation
An Arsenal reviewer pointed out the README jumps to the catalog without first saying what the tool does. Lead with the least-privilege description: runtime interception via PreToolUse/PostToolUse, out-of-model enforcement, what the safety set blocks, and the OWASP mapping link.
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.
A Black Hat Arsenal reviewer suggested the README should lead with the tool description so visitors orient quickly. This adds one paragraph after the badges: what agents do autonomously, how hooks intercept every tool call (allow/deny/modify with the reason fed back), why out-of-model enforcement resists prompt injection, what the safety set blocks, and the OWASP LLM Top 10 2026 mapping link.
No content below the intro changed. Claims cross-checked against the plugin catalog (block-dangerous-commands covers curl|sh, rm -rf, force push to main; config-guard covers hook-config tampering; protect-secrets covers .env exfiltration).