Agent settings with automatic actions at session start, before edits, and after writes, plus safeguards around publishing and snapshot files.

They are for managing session setup, guarding edits, checking license headers, and requiring approval before pushes, releases, package publishing, or tags.

They provide project context, protect test snapshots before changes, and check written files for required SPDX license information.

fsl — Settings file by ymm-oss

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/ymm-oss/fsl/settings

Clone the repo

git clone --depth 1 https://github.com/ymm-oss/fsl

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 A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

fsl 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 2d 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 · 51 lines

What it actually says

{
  "permissions": {
    "defaultMode": "default",
    "ask": [
      "Bash(git push *)",
      "Bash(git tag *)",
      "Bash(gh pr create *)",
      "Bash(gh release create *)",
      "Bash(cargo publish *)",
      "Bash(npm publish *)"
    ],
    "deny": [
      "Edit(/tests/snapshots/corpus_snapshot.json)"
    ]
  },
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"${CLAUDE_PROJECT_DIR}/.claude/hooks/session_context.py\""
          }
        ]
      }
    ],
    "PreToolUse": [
      {
        "matcher": "Edit|Write",
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"${CLAUDE_PROJECT_DIR}/.claude/hooks/snapshot_guard.py\""
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Write",
        "hooks": [
          {
            "type": "command",
            "command": "python3 \"${CLAUDE_PROJECT_DIR}/.claude/hooks/spdx_guard.py\""
          }
        ]
      }
    ]
  }
}

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.

2d ago First seen · 51 lines scan A fd4a2e6e143c

Subscribe to this mod's changes

fsl is a settings file published in the GitHub repository ymm-oss/fsl (21 stars, last pushed 4d ago), licensed Apache-2.0. 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-30.

Data and AI LLM Languages bounded-model-checking formal-methods formal-specification model-checking python

fsl

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other settings, from other repositories

scitex-python

Dense-Evolution

settings

Q4_learning

settings

supabase