Borrowing it
Nothing to install: this file belongs to usk6666/yorishiro-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/usk6666/yorishiro-proxy/main/.claude/settings.jsongit clone --depth 1 https://github.com/usk6666/yorishiro-proxyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/settings/usk6666/yorishiro-proxy/settings)<a href="https://agentmods.dev/settings/usk6666/yorishiro-proxy/settings"><img src="https://agentmods.dev/badge/settings/usk6666/yorishiro-proxy/settings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/settings/usk6666/yorishiro-proxy/settings"><img src="https://agentmods.dev/badge/settings/usk6666/yorishiro-proxy/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade D, and why
yorishiro-proxy scanned grade D 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
"Bash(go tool:*)", 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 /)", Copies of this mod
1 near-identical copy found in the catalogue:
- mcp-for-argo-workflows — 86% identical, 291 lines differ
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"permissions": {
"allow": [
"Skill(*)",
"WebSearch",
"Bash(cat:*)",
"Bash(cd:*)",
"Bash(diff:*)",
"Bash(file:*)",
"Bash(grep:*)",
"Bash(head:*)",
"Bash(jq:*)",
"Bash(ls:*)",
"Bash(mkdir:*)",
"Bash(pwd)",
"Bash(rg:*)",
"Bash(sed -n:*)",
"Bash(sort:*)",
"Bash(tail:*)",
"Bash(uniq:*)",
"Bash(wc:*)",
"Bash(which:*)",
"Bash(git add:*)",
"Bash(git blame:*)",
"Bash(git branch:*)",
"Bash(git checkout:*)",
"Bash(git commit:*)",
"Bash(git describe:*)",
"Bash(git diff:*)",
"Bash(git fetch:*)",
"Bash(git grep:*)",
"Bash(git log:*)",
"Bash(git ls-files:*)",
"Bash(git merge-base:*)",
"Bash(git mv:*)",
"Bash(git pull:*)",
"Bash(git push -u origin:*)",
"Bash(git push origin:*)",
"Bash(git reflog:*)",
"Bash(git remote -v)",
"Bash(git rev-parse:*)",
"Bash(git rm:*)",
"Bash(git shortlog:*)",
"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 tag -l:*)",
"Bash(git worktree:*)",
"Bash(gh auth status)",
"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 release list:*)",
"Bash(gh release view:*)",
"Bash(gh repo view:*)",
"Bash(gh run list:*)",
"Bash(gh run view:*)",
"Bash(gh run watch:*)",
"Bash(gh search code:*)",
"BasWhat 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 Changed · +2 lines 05beb5ae9ff8
- 3d ago Changed · +1 lines c1dafaa2a935
- 13d ago Changed · +1 lines 13f6a489b437
- 1mo ago Changed · +47 lines scan C → D 8247a1f4ee05
- 1mo ago Changed cf2d36106587
- 1mo ago First seen · 178 lines scan C c3b5d6f7431f
yorishiro-proxy is a settings file published in the GitHub repository usk6666/yorishiro-proxy (19 stars, last pushed yesterday), 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 D with 2 findings (unrestricted tool access, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other settings, from other repositories
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
superset
Agent settings declaring 1 hook event (PreToolUse).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.
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.