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/fmflurry/settings-opencode/settingsgit clone --depth 1 https://github.com/fmflurry/settings-opencodeGrade B, and why
settings-opencode scanned grade B with 1 finding 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
"Bash(chmod 777*)" How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"env": {
"API_TIMEOUT_MS": "3000000",
"CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC": "1",
"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "80",
"CI": "true"
},
"attribution": {
"commit": "",
"pr": ""
},
"permissions": {
"allow": [
"Read",
"Write",
"Edit",
"Glob",
"Grep",
"Bash",
"AskUserQuestion",
"Task",
"TaskCreate",
"TaskGet",
"TaskUpdate",
"TaskList"
],
"deny": [
"Write(*.env)",
"Write(*secrets*)",
"Write(*.key)",
"Write(*.pem)",
"Write(*credentials*)",
"Edit(*.env)",
"Edit(*secrets*)",
"Edit(*.key)",
"Edit(*.pem)",
"Edit(*credentials*)",
"Bash(sudo*)",
"Bash(*> /dev/)",
"Bash(chmod 777*)"
]
},
"hooks": {
"PreToolUse": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/pre-tool-use.sh"
}
]
},
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "/Users/fmflurry/.claude/hooks/rtk-rewrite.sh"
}
]
},
{
"matcher": "Grep|Glob|Bash",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/prefer-code-memory.sh"
}
]
},
{
"matcher": "Bash|Edit|Write|MultiEdit",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/tool-budget.sh"
}
]
}
],
"Stop": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/stop.sh"
}
]
}
],
"Notification": [
{
"matcher": "*",
"hooks": [
{
"type": "command",
"command": "~/.claude/hooks/notification.sh"
}
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.
- yesterday First seen · 133 lines scan B eeaab58eab75
settings-opencode is a settings file published in the GitHub repository fmflurry/settings-opencode (172 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it B with 1 finding (asks for root). 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).
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.
electron
Agent settings declaring 17 allowed tools.
uv
Agent settings declaring 2 hook events (SessionStart, PostToolUse).
ui-ux-pro-max-skill
Agent settings declaring 7 allowed tools.