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/znlnzi/claude-config-studio/settingsgit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/znlnzi/claude-config-studio/settings)<a href="https://agentmods.dev/settings/znlnzi/claude-config-studio/settings"><img src="https://agentmods.dev/badge/settings/znlnzi/claude-config-studio/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
settings 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 3d 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
{
"enableAllProjectMcpServers": true,
"env": {
"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"
},
"hooks": {
"SessionStart": [
{
"hooks": [
{
"type": "command",
"command": "bash scripts/detect-project.sh"
}
]
}
],
"PreCompact": [
{
"matcher": "auto",
"hooks": [
{
"type": "command",
"command": "bash scripts/pre-compact-save.sh"
}
]
}
],
"Stop": [
{
"hooks": [
{
"type": "command",
"command": "bash scripts/check-memory-saved.sh"
}
]
}
]
}
}
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.
- 3d ago First seen · 40 lines scan A 75b6a1857236
settings is a settings file published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other settings, from other repositories
Hades
Agent settings declaring 5 allowed tools.
humanasllm
Agent settings declaring 1 hook event (PreToolUse).
settings
Agent settings declaring 4 hook events (SessionStart, PreToolUse, PostToolUse, PostToolUseFailure).
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).