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/wolfpackofone/q-agent/settingsgit clone --depth 1 https://github.com/WolfpackOfOne/Q-agentGrade A, and why
Q-agent scanned grade A with 0 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 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
75% identical to settings — 56 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
{
"permissions": {
"allow": [
"Bash(git status:*)",
"Bash(git branch:*)",
"Bash(git ls-remote:*)",
"Bash(git check-ignore:*)",
"Bash(gh repo:*)",
"Bash(gh gist:*)",
"Bash(gh auth:*)",
"Bash(ls *)",
"Bash(wc *)",
"Bash(head *)",
"Bash(cat > *)",
"Bash(mkdir *)",
"Bash(cd *)",
"Bash(source *)",
"Bash(env)",
"WebSearch"
]
},
"hooks": {
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/stop-memory-nudge.sh"
}
]
}
],
"SessionStart": [
{
"matcher": "startup|resume|clear|compact",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/load_memory.py"
}
]
}
],
"PostToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/log_tool_event.py"
}
]
}
],
"SessionEnd": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/extract_session_memory.py"
}
]
}
]
}
}
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 · 68 lines scan A 62eeb622c36f
Q-agent is a settings file published in the GitHub repository WolfpackOfOne/Q-agent (5 stars, last pushed 1mo 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 A with 0 findings. It is 75% identical to settings, differing in 56 lines, and is treated as a copy.
Other settings, from other repositories
quant-mind
Agent settings declaring 1 hook event (PreToolUse).
investor-bot
Agent settings declaring 1 hook event (PostToolUse).
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.