clawstash: Settings file for Claude Code

.claude/settings.json

clawstash is a settings file for Claude Code from fo0/clawstash. Its token cost is not measured, scanned A, original, MIT.

A Claude Code settings file defining allowed tools and automated actions that run when a session starts or after tools edit files. It also includes a rule for checking the size of selected project memory and scratch files.

In plain words
What is it for?
Use it to configure Claude Code permissions, session-start messages, post-edit checks, and allowed formatting, linting, type-checking, testing, and build commands.
Why use it?
It sets project-specific tool permissions and reminders, helping keep recurring checks and session-start instructions consistent.

Settings file for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: mentions CLAUDE.md; positional $N argument.

This is fo0/clawstash's own configuration. It tells Claude Code how to work on clawstash 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 clawstash 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 fo0/clawstash. 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/fo0/clawstash/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/fo0/clawstash

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 clawstash

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

Your own site · 80×15
<a href="https://agentmods.dev/settings/fo0/clawstash/settings"><img src="https://agentmods.dev/badge/settings/fo0/clawstash/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

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

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 · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "$schema": "https://json.schemastore.org/claude-code-settings.json",
  "permissions": {
    "allow": [
      "mcp__claude-code-remote__*",
      "mcp__Claude_Code_Remote__*",
      "mcp__claude_code_remote__*",
      "mcp__github__subscribe_pr_activity",
      "mcp__github__unsubscribe_pr_activity",
      "Bash(npm install)",
      "Bash(npm run format)",
      "Bash(npm run format:check)",
      "Bash(npm run lint)",
      "Bash(npx tsc --noEmit)",
      "Bash(npm test)",
      "Bash(npm run build)"
    ]
  },
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "echo 'Session start -- read MEMORY.md and SCRATCHPAD.md to restore context. Check BACKLOG.md only if user references prior findings.'"
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": "over=\"\"; for spec in \"CLAUDE.md 14000\" \"MEMORY.md 16000\" \"SCRATCHPAD.md 8000\"; do set -- $spec; f=\"$CLAUDE_PROJECT_DIR/$1\"; [ -f \"$f\" ] || continue; c=$(wc -c < \"$f\"); [ \"$c\" -gt \"$2\" ] && over=\"$over $1 $c/$2 chars;\"; done; if [ -n \"$over\" ]; then printf '%s' '{\"hookSpecificOutput\":{\"hookEventName\":\"PostToolUse\",\"additionalContext\":\"Context budget exceeded --'\"$over\"' offload now per agent_docs/context_budget.md: MOVE content out (CLAUDE.md sections to agent_docs/, memory entries to docs/adr/ or agent_docs/memory_archive/) and leave a one-line pointer. Never delete to fit.\"}}'; fi; exit 0"
          }
        ]
      }
    ],
    "PreToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": "command -v jq >/dev/null 2>&1 || { printf '%s' '{\"hookSpecificOutput\":{\"hookEventName\":\"PreToolUse\",\"additionalContext\":\"Quality-config guard is inert on this machine: jq is not installed, so the hook cann

Read the full file on GitHub · 54 lines

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. 1mo ago Changed · -9 lines scan B → A 1479750af48e
  2. 1mo ago Changed 9fae4b99bb82
  3. 1mo ago Changed · +10 lines a2ce75a09451
  4. 2mo ago First seen · 53 lines scan B 1ca82e1ee360

Subscribe to this mod's changes

clawstash is a settings file published in the GitHub repository fo0/clawstash (1 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.