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/ai4curation/ai-gene-review/settingsgit clone --depth 1 https://github.com/ai4curation/ai-gene-reviewWrote 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/ai4curation/ai-gene-review/settings)<a href="https://agentmods.dev/settings/ai4curation/ai-gene-review/settings"><img src="https://agentmods.dev/badge/settings/ai4curation/ai-gene-review/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ai-gene-review 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 6d 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.
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.
What it actually says
{
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "set -o pipefail; uv tool install rust-just 2>&1 | tail -1 && cd $CLAUDE_PROJECT_DIR && uv sync --group dev 2>&1 | tail -5"
}
]
}
],
"PostToolUse": [
{
"matcher": "Edit|MultiEdit|Write",
"hooks": [
{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/validate_ai_review_hook.py"
},
{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/validate_rule_review_hook.py"
}
]
}
],
"PreToolUse": [
{
"matcher": "Edit|MultiEdit|Write",
"hooks": [
{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/protect_files_hook.py"
},
{
"type": "command",
"command": "$CLAUDE_PROJECT_DIR/.claude/hooks/validate_ai_review_pretool_hook.py"
}
]
}
]
}
}What else settings.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 6d ago First seen · 44 lines scan A 8a8bbda9ce8f
ai-gene-review is a settings file published in the GitHub repository ai4curation/ai-gene-review (24 stars, last pushed today), licensed BSD-3-Clause. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other settings, from other repositories
dismech
Agent settings declaring 1 hook event (PreToolUse) and 36 allowed tools.
github-ai-integrations
Agent settings declaring 8 allowed tools.
bbop-skills
Agent settings declaring 8 allowed tools.
claude-agent-sdk-go
Agent settings declaring 20 allowed tools.
Q4_learning
Agent settings declaring 4 allowed tools.
supabase
Agent settings declaring 2 hook events (SessionStart, PostToolUse).