claude-omo-agentflow: Settings file for Claude Code

.claude/settings.json

claude-omo-agentflow is a settings file for Claude Code from wangjialiang678/claude-omo-agentflow. Its token cost is not measured, scanned A, original, MIT.

Agent settings that define scripts for stopping, ending subagents, and preparing for context compaction, plus one allowed shell command. A subagent is a smaller assistant process working on part of a task.

In plain words
What is it for?
Use it to run stop, subagent-stop, and pre-compact scripts, and to permit the du command for checking disk usage.
Why use it?
It automates cleanup and context handling at key points in an agent session while limiting the explicitly allowed command.

Settings file for Claude Code

Written for Claude Code: SubagentStop hook event. Also seen: reads .claude/ paths; mentions subagents.

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

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 claude-omo-agentflow

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

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

claude-omo-agentflow 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 · 43 lines

What it actually says

{
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/stop.sh",
            "timeout": 10
          }
        ]
      }
    ],
    "SubagentStop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/subagent-stop.sh",
            "timeout": 10
          }
        ]
      }
    ],
    "PreCompact": [
      {
        "hooks": [
          {
            "type": "command",
            "command": ".claude/hooks/pre-compact.sh",
            "timeout": 10
          }
        ]
      }
    ]
  },
  "permissions": {
    "allow": [
      "Bash(du:*)"
    ]
  }
}
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 First seen · 43 lines scan A 1c1a2e345ea5

Subscribe to this mod's changes

claude-omo-agentflow is a settings file published in the GitHub repository wangjialiang678/claude-omo-agentflow (2 stars, last pushed 8mo 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 A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.