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/brianmontanaweb/agentic-design-system/settingsgit clone --depth 1 https://github.com/brianmontanaweb/agentic-design-systemWrote 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/brianmontanaweb/agentic-design-system/settings)<a href="https://agentmods.dev/settings/brianmontanaweb/agentic-design-system/settings"><img src="https://agentmods.dev/badge/settings/brianmontanaweb/agentic-design-system/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agentic-design-system 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
{
"permissions": {
"allow": [
"WebSearch",
"WebFetch(domain:github.com)",
"WebFetch(domain:www.npmjs.com)",
"WebFetch(domain:storybook.js.org)",
"Bash(npm run:*)",
"Bash(npm view:*)",
"Bash(npx prettier --write:*)",
"Bash(npx eslint:*)",
"Bash(git add:*)",
"Bash(git commit:*)",
"Bash(git remote:*)",
"Bash(git push:*)",
"Bash(gh auth:*)",
"Edit(/.claude/skills/**)"
],
"additionalDirectories": []
},
"enableAllProjectMcpServers": true,
"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "file=$(echo $CLAUDE_TOOL_INPUT | node -e \"process.stdin.resume();let d='';process.stdin.on('data',c=>d+=c);process.stdin.on('end',()=>{try{console.log(JSON.parse(d).file_path||'')}catch(e){}})\"); if [[ \"$file\" == *.ts || \"$file\" == *.tsx || \"$file\" == *.json || \"$file\" == *.md ]]; then npx prettier --write \"$file\" 2>/dev/null; fi"
}
]
}
]
},
"enabledPlugins": {
"skill-creator@claude-plugins-official": true
}
}
What else settings.json configures
This page is one entry in a file that holds 2. 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 · 39 lines scan A acfd1b2f0b6d
agentic-design-system is a settings file published in the GitHub repository brianmontanaweb/agentic-design-system (2 stars, last pushed 13d 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
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).
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).