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/arnabdeypolimi/claude_code_setup/settingsgit clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setupGrade A, and why
claude_code_setup 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
81% identical to scalar — 16 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
{
"enabledPlugins": {
"frontend-design@claude-plugins-official": true,
"superpowers@claude-plugins-official": true,
"context7@claude-plugins-official": true,
"code-review@claude-plugins-official": true,
"code-simplifier@claude-plugins-official": true,
"github@claude-plugins-official": true,
"playwright@claude-plugins-official": true,
"skill-creator@claude-plugins-official": true,
"claude-md-management@claude-plugins-official": true,
"security-guidance@claude-plugins-official": true,
"pr-review-toolkit@claude-plugins-official": true,
"gitlab@claude-plugins-official": true,
"huggingface-skills@claude-plugins-official": true,
"firebase@claude-plugins-official": true,
"ui-ux-pro-max@ui-ux-pro-max-skill": true,
"claude-mem@thedotmack": true
}
}
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 · 21 lines scan A 3563005f6b6c
claude_code_setup is a settings file published in the GitHub repository arnabdeypolimi/claude_code_setup (4 stars, last pushed 3mo 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 81% identical to scalar, differing in 16 lines, and is treated as a copy.
Other settings, from other repositories
exosuit
Agent settings declaring 10 hook events (SessionStart, PreToolUse, PostToolUse, Stop).
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).