Borrowing it
Nothing to install: this file belongs to agentpipe/pipebuilder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agentpipe/pipebuilder/main/.pipe-agents/claude-code/.claude/settings.jsongit clone --depth 1 https://github.com/agentpipe/pipebuilderWrote 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/agentpipe/pipebuilder/settings)<a href="https://agentmods.dev/settings/agentpipe/pipebuilder/settings"><img src="https://agentmods.dev/badge/settings/agentpipe/pipebuilder/settings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/settings/agentpipe/pipebuilder/settings"><img src="https://agentmods.dev/badge/settings/agentpipe/pipebuilder/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade B, and why
pipebuilder scanned grade B with 1 finding 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 2mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
"Edit(/.claude/settings.json)", What it actually says
{
"permissions": {
"deny": [
"Edit(/AGENTS.md)",
"Edit(/CLAUDE.md)",
"Edit(/.agents/skills/**)",
"Edit(/.cursor/skills/**)",
"Edit(/.codebuddy/skills/**)",
"Edit(/.codebuddy/settings.json)",
"Edit(/.claude/skills/**)",
"Edit(/.claude/settings.json)",
"Edit(/.pipebuilder/generated/**)",
"Edit(/.pipebuilder/lock.json)",
"Edit(/.pipebuilder/tree-lock.json)",
"Edit(/.pipebuilder/tree-journal.json)"
]
}
}
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.
- 2mo ago First seen · 19 lines scan B 13adcd9241de
pipebuilder is a settings file published in the GitHub repository agentpipe/pipebuilder (3 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 B with 1 finding (reads agent configuration directories). 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).
RuView
Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.
claude-cookbooks
Agent settings declaring 2 hook events (SessionStart, PreToolUse).
orm
Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.
claude-code-best-practice
Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.