agentmods.dev

ccswarm: Settings file for Claude Code

.claude/settings.json

ccswarm is a settings file for Claude Code from nwiizo/ccswarm. Its token cost is not measured, scanned C, original, MIT.

An agent-settings file that defines four hook events and a list of permitted or blocked tools. Hooks are commands that run when specified agent events occur.

In plain words
What is it for?
Use it to configure permissions for reading, editing, Git, Rust, database tools, and specialist agents, plus checks before and after file changes.
Why use it?
It makes tool access and automated checks explicit, including formatting, scope validation, and restrictions on risky commands or files.

Settings file for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths.

This is nwiizo/ccswarm's own configuration. It tells Claude Code how to work on ccswarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ccswarm configures →

One of 5 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 4 are separate, each on its own page.

not rated 153repo 7d ago C scan tokens not measured original MIT
View source ↗ nwiizo/ccswarm
Reuse

Borrowing it

Nothing to install: this file belongs to nwiizo/ccswarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nwiizo/ccswarm/master/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/nwiizo/ccswarm

Made for: Claude Code.

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

agentmods badge for ccswarm

README.md
[![agentmods](https://agentmods.dev/badge/settings/nwiizo/ccswarm/settings/github.svg)](https://agentmods.dev/settings/nwiizo/ccswarm/settings)
Your own site
<a href="https://agentmods.dev/settings/nwiizo/ccswarm/settings"><img src="https://agentmods.dev/badge/settings/nwiizo/ccswarm/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.

agentmods 80×15 button for ccswarm

Your own site · 80×15
<a href="https://agentmods.dev/settings/nwiizo/ccswarm/settings"><img src="https://agentmods.dev/badge/settings/nwiizo/ccswarm/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade C, and why

ccswarm scanned grade C 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 1mo 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"Bash(rm -rf /)*",
.claude/settings.json · 84 lines

What it actually says

{
  "permissions": {
    "allow": [
      "Read",
      "Glob",
      "Grep",
      "Bash(cargo *)",
      "Bash(git status*)",
      "Bash(git diff*)",
      "Bash(git log*)",
      "Bash(git branch*)",
      "Bash(git worktree *)",
      "Bash(ls *)",
      "Bash(wc *)",
      "Bash(similarity-rs *)",
      "mcp__serena__*",
      "Agent(Explore)",
      "Agent(frontend-specialist)",
      "Agent(backend-specialist)",
      "Agent(devops-specialist)",
      "Agent(qa-specialist)",
      "Agent(rust-fix-agent)",
      "Agent(code-refactor-agent)",
      "Agent(architecture-reviewer)",
      "Agent(all-reviewer)",
      "Agent(review-fix-agent)"
    ],
    "deny": [
      "Bash(rm -rf /)*",
      "Bash(cargo publish*)",
      "Edit(.git/***)",
      "Edit(.env*)"
    ]
  },
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/validate-agent-scope.sh"
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/format-code.sh"
          }
        ]
      }
    ],
    "SubagentStop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/audit-trail.sh"
          }
        ]
      }
    ],
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/audit-trail.sh"
          }
        ]
      }
    ]
  },
  "env": {
    "RUST_LOG": "info",
    "CCSWARM_AUDIT_ENABLED": "true"
  }
}
Same file

What else settings.json configures

This page is one entry in a file that holds 5. Installing the file brings all of them; each is measured and scanned on its own page.

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. 1mo ago First seen · 84 lines scan C 591e7254790a

Subscribe to this mod's changes

ccswarm is a settings file published in the GitHub repository nwiizo/ccswarm (153 stars, last pushed 7d 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 C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other settings, from other repositories

supabase

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

supabase/supabase · not measured

superset

Agent settings declaring 1 hook event (PreToolUse).

apache/superset · not measured

RuView

Agent settings declaring 8 hook events (PreToolUse, PostToolUse, UserPromptSubmit, SessionStart) and 4 allowed tools.

ruvnet/RuView · not measured

orm

Agent settings declaring 4 hook events (PreToolUse, PostToolUse, WorktreeCreate, Stop) and 21 allowed tools.

prisma/orm · 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