A settings file for an agent setup. It defines actions that run when the agent stops or a work session ends, including a command that uploads activity traces.

Use it to configure stop and session-end hooks and enable a plug-in in the agent settings.

It centralizes these automatic session actions so they can run consistently without being repeated manually.

clarity — Settings file by SchroederNathan

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/schroedernathan/clarity/settings

Clone the repo

git clone --depth 1 https://github.com/SchroederNathan/clarity

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

clarity 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 · 30 lines

What it actually says

{
  "enabledPlugins": {
    "expo@claude-plugins-official": true
  },
  "hooks": {
    "Stop": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "SSL_CERT_FILE=/etc/ssl/cert.pem python3 ~/.hackathon-trace/trace_upload.py --agent claude-code",
            "timeout": 30
          }
        ]
      }
    ],
    "SessionEnd": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "SSL_CERT_FILE=/etc/ssl/cert.pem python3 ~/.hackathon-trace/trace_upload.py --agent claude-code",
            "timeout": 30
          }
        ]
      }
    ]
  }
}

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 · 30 lines scan A 09ce11f59a56

Subscribe to this mod's changes

clarity is a settings file published in the GitHub repository SchroederNathan/clarity (312 stars, last pushed 2d 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-30.

Frontend Mobile expo react-native speech

GardenPulse

Method-agnostic smart garden companion built with React Native, Expo, and TypeScript. Adapts to soil, hydro, container, or indoor setups with location-aware intelligence, OpenWeather integration, and privacy-first, on-device Gemini AI plant diagnostics.

AhmadHassan-BTed/GardenPulse · not measured

clarity

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

GardenPulse

react-native-fsd-agent-template

arc-skill

expense-mcp

supabase

claude-cookbooks