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/artemiopadilla/love-claude-code/settingsgit clone --depth 1 https://github.com/ArtemioPadilla/love-claude-codeWrote 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/artemiopadilla/love-claude-code/settings)<a href="https://agentmods.dev/settings/artemiopadilla/love-claude-code/settings"><img src="https://agentmods.dev/badge/settings/artemiopadilla/love-claude-code/settings.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
love-claude-code 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 4d 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": {
"PreToolUse": [
{
"name": "tdd-guard",
"description": "Enforce TDD principles before file operations",
"matcher": "Write|Edit|MultiEdit|TodoWrite",
"command": "tdd-guard",
"timeout": 5000,
"config": {
"enabled": true,
"testFramework": "vitest",
"watchPatterns": [
"frontend/src/**/*.ts",
"frontend/src/**/*.tsx",
"backend/src/**/*.ts"
],
"excludePatterns": [
"node_modules/**",
"dist/**",
"coverage/**",
"**/*.test.ts",
"**/*.spec.ts"
],
"strictness": "medium",
"allowRefactoring": true,
"phases": {
"red": {
"allowedFiles": ["**/*.test.ts", "**/*.spec.ts", "**/*.test.tsx"],
"message": "🔴 Red phase: Write failing tests first"
},
"green": {
"allowedFiles": ["**/*.ts", "**/*.tsx"],
"excludeFiles": ["**/*.test.ts", "**/*.spec.ts"],
"message": "🟢 Green phase: Make tests pass with minimal code"
},
"refactor": {
"allowedFiles": ["**/*.ts", "**/*.tsx"],
"message": "🔵 Refactor phase: Improve code quality"
}
}
}
}
]
},
"mcpServers": {
"playwright-automation": {
"command": "npx",
"args": ["@modelcontextprotocol/server-playwright"],
"env": {
"PLAYWRIGHT_HEADLESS": "false",
"PLAYWRIGHT_BROWSER": "chromium",
"PLAYWRIGHT_TIMEOUT": "30000"
},
"description": "Playwright browser automation for E2E testing"
}
}
}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.
- 4d ago First seen · 58 lines scan A 444841dc397c
love-claude-code is a settings file published in the GitHub repository ArtemioPadilla/love-claude-code (5 stars, last pushed 4mo 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).