Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add settings/usk6666/yorishiro-proxy/settingsgit clone --depth 1 https://github.com/usk6666/yorishiro-proxyGrade C, and why
yorishiro-proxy scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
"Bash(rm -rf /)", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"Bash(curl:*)", Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-for-argo-workflows — 86% identical, 242 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"permissions": {
"allow": [
"Skill(*)",
"WebSearch",
"Bash(./node_modules/.bin/tsc:*)",
"Bash(./node_modules/.bin/vite build:*)",
"Bash(cat:*)",
"Bash(cd:*)",
"Bash(gh issue list:*)",
"Bash(gh issue view:*)",
"Bash(gh pr checks:*)",
"Bash(gh pr checkout:*)",
"Bash(gh pr comment:*)",
"Bash(gh pr create:*)",
"Bash(gh pr diff:*)",
"Bash(gh pr edit:*)",
"Bash(gh pr list:*)",
"Bash(gh pr ready:*)",
"Bash(gh pr review:*)",
"Bash(gh pr status)",
"Bash(gh pr update-branch:*)",
"Bash(gh pr view:*)",
"Bash(gh repo view:*)",
"Bash(gh run list:*)",
"Bash(gh run view:*)",
"Bash(gh run watch:*)",
"Bash(gh search code:*)",
"Bash(gh search issues:*)",
"Bash(gh search prs:*)",
"Bash(git add:*)",
"Bash(git blame:*)",
"Bash(git branch --list:*)",
"Bash(git branch --show-current)",
"Bash(git branch -a)",
"Bash(git branch:*)",
"Bash(git checkout:*)",
"Bash(git commit:*)",
"Bash(git diff:*)",
"Bash(git fetch:*)",
"Bash(git grep:*)",
"Bash(git log:*)",
"Bash(git mv:*)",
"Bash(git pull:*)",
"Bash(git push -u origin:*)",
"Bash(git push origin:*)",
"Bash(git rm:*)",
"Bash(git show:*)",
"Bash(git stash)",
"Bash(git stash list)",
"Bash(git stash pop)",
"Bash(git stash push:*)",
"Bash(git stash show:*)",
"Bash(git status:*)",
"Bash(git switch:*)",
"Bash(git worktree:*)",
"Bash(go build:*)",
"Bash(go doc:*)",
"Bash(go env:*)",
"Bash(go list:*)",
"Bash(go mod download)",
"Bash(go mod graph)",
"Bash(go mod tidy)",
"Bash(go test:*)",
"Bash(go version)",
"Bash(go vet:*)",
"Bash(gocyclo:*)",
"Bash(gofmt:*)",
"Bash(goimports:*)",
"Bash(grep:*)",
"Bash(head:*)",
"Bash(ineffassign:*)",
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 178 lines scan C c3b5d6f7431f
yorishiro-proxy is a settings file published in the GitHub repository usk6666/yorishiro-proxy (16 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other settings, from other repositories
telepresence
Agent settings declaring 2 hook events (PreToolUse, PostToolUse).
dynamic-mcp
Agent settings configuring enabledMcpjsonServers, enableAllProjectMcpServers, enabledPlugins.
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.