agentmods.dev

pipebuilder

A settings file that defines which project files and directories agents are not allowed to edit.

In plain words
What is it for?
Use it to deny edits to files such as AGENTS.md, CLAUDE.md, skill directories, agent settings, and Pipebuilder's generated state.
Why use it?
It protects instructions, skill definitions, settings, and generated pipeline files from accidental changes.

Settings file for Claude Code

2 1mo ago B scan tokens not measured original MIT
View the source file agentpipe/pipebuilder
Install

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.

agentmods
npx agentmods add settings/agentpipe/pipebuilder/settings
Clone the repo
git clone --depth 1 https://github.com/agentpipe/pipebuilder

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

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 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.

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)",
.pipe-agents/claude-code/.claude/settings.json · 19 lines

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)"
    ]
  }
}
Changes

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.

  1. yesterday First seen · 19 lines scan B 13adcd9241de

Subscribe to this mod's changes

pipebuilder is a settings file published in the GitHub repository agentpipe/pipebuilder (2 stars, last pushed 1mo 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.

agent-pipelineagent-skillsai-coding-agentsclaude-codeclaude-code-skillscodebuddy
Related

Other settings, from other repositories

settings

Agent settings declaring 2 hook events (PreToolUse, PostToolUse) and 2 allowed tools.

clever-cc-plugins/cc-content · not measured

supabase

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

supabase/supabase · not measured

claude-cookbooks

Agent settings declaring 2 hook events (SessionStart, PreToolUse).

anthropics/claude-cookbooks · not measured

claude-code-best-practice

Agent settings declaring 30 hook events (PreToolUse, PermissionRequest, PostToolUse, PostToolUseFailure) and 24 allowed tools.

shanraisshan/claude-code-best-practice · not measured

electron

Agent settings declaring 17 allowed tools.

electron/electron · not measured

uv

Agent settings declaring 2 hook events (SessionStart, PostToolUse).

astral-sh/uv · not measured