mangrove-agent: Settings file for Claude Code

.claude/settings.json

mangrove-agent is a settings file for Claude Code from MangroveTechnologies/mangrove-agent. Its token cost is not measured, scanned A, original, MIT.

Agent settings that run command hooks when prompts are submitted, tools finish, or tools are about to run.

In plain words
What is it for?
Protecting sensitive wallet data, preventing selected commits, and checking swap operations before execution.
Why use it?
They can block wallet secrets and main-branch commits, and run a preflight check before a swap command.

Settings file for Claude Code

Written for Claude Code: ${CLAUDE_PROJECT_DIR} variable.

This is MangroveTechnologies/mangrove-agent's own configuration. It tells Claude Code how to work on mangrove-agent 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 mangrove-agent configures →

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

Reuse

Borrowing it

Nothing to install: this file belongs to MangroveTechnologies/mangrove-agent. 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/MangroveTechnologies/mangrove-agent/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/MangroveTechnologies/mangrove-agent

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 mangrove-agent

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

Your own site · 80×15
<a href="https://agentmods.dev/settings/mangrovetechnologies/mangrove-agent/settings"><img src="https://agentmods.dev/badge/settings/mangrovetechnologies/mangrove-agent/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 A 0 findings. 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 A, and why

mangrove-agent 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 13d 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.

.claude/settings.json · 52 lines

What it actually says

{
  "hooks": {
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "\"${CLAUDE_PROJECT_DIR}/.claude/hooks/block-wallet-secrets.sh\" --mode user",
            "timeout": 3
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "\"${CLAUDE_PROJECT_DIR}/.claude/hooks/block-wallet-secrets.sh\" --mode tool",
            "timeout": 3
          }
        ]
      }
    ],
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "\"${CLAUDE_PROJECT_DIR}/.claude/hooks/block-main-commits.sh\"",
            "timeout": 3
          }
        ]
      },
      {
        "matcher": "mcp__mangrove-agent__execute_swap",
        "hooks": [
          {
            "type": "command",
            "command": "\"${CLAUDE_PROJECT_DIR}/.claude/hooks/preflight-swap.sh\"",
            "timeout": 5
          }
        ]
      }
    ]
  },
  "permissions": {
    "defaultMode": "default"
  }
}
Same file

What else settings.json configures

This page is one entry in a file that holds 4. 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. 13d ago Changed · +3 lines cb1f2750e785
  2. 1mo ago First seen · 49 lines scan A e62d0dcef7a1

Subscribe to this mod's changes

mangrove-agent is a settings file published in the GitHub repository MangroveTechnologies/mangrove-agent (5 stars, last pushed today), 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.