CLAUDE

A data-based definition for an AI agent: a JSON file describing its identity, the events it receives, and the reports it produces. A seed script reads these definitions and adds them to a D1 database.

In plain words
What is it for?
Use it to define an agent's ID, description, subscriptions, persona, and reporting behavior before loading it into the dashboard's database.
Why use it?
It lets teams configure agents as data instead of writing each agent directly into application code.

Agent

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 agents/serpin-taxt/openchief/claude
Clone the repo
git clone --depth 1 https://github.com/serpin-taxt/openchief
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,312 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02312
Opus 5 $0.00000 $0.01156
Sonnet 5 $0.00000 $0.00462
Haiku 4.5 $0.00000 $0.00231

Measured 3d ago against content hash 84ed5c26ffe1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

CLAUDE 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 3d 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.

agents/CLAUDE.md · 189 lines

How it starts

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

agents/ — Agent Definitions

Agent definitions are data, not code. Each JSON file in this directory defines an AI agent's identity, what data it watches, and what reports it produces. The seed script (pnpm seed) reads all .json files from this directory and inserts them into D1.

Agent Definition Schema

Every agent JSON file must have these fields:

{
  // Identity
  "id": string,           // Unique kebab-case ID (matches filename without .json)
  "name": string,          // Human-readable display name
  "description": string,   // What this agent watches and does (shown in dashboard)

  // Data Sources
  "subscriptions": [       // Which events this agent receives
    {
      "source": string,        // Must match a connector source: "github", "slack", etc.
      "eventTypes": string[],  // Wildcard patterns: "pr.*", "message.*", "*"
      "scopeFilter"?: {        // Optional narrowing (AND logic)
        "org"?: string,
        "project"?: string,
        "team"?: string
      }
    }
  ],

  // Claude's Identity
  "persona": {
    "role": string,            // System prompt identity (1 sentence)
    "instructions": string,    // Detailed analysis guidelines (Markdown, can be long)
    "watchPatterns": string[], // Specific things to flag/escalate
    "outputStyle": string,     // How to format and tone the output
    "voice"?: string,          // Communication style and vocabulary
    "personality"?: string     // Temperament, values, quirks
  },

  // Report Configuration
  "outputs": {
    "reports": [
      {
        "reportType": string,    // Unique type ID: "daily-standup", "daily-metrics-brief"
        "cadence": "daily",
        "sections": string[]     // Section names Claude must include
      }
    ]
  },

  // Capabilities
  "enabled": boolean,          // Whether the agent actively generates reports
  "tools"?: string[],          // Optional: ["query_events", "github_file", "github_search"]

  // Access Control
  "visibility"?: "public" | "exec"  // Default: "public". See "Exec Visibility" below.
}

Read the full file on GitHub · 189 lines

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. 3d ago First seen · 189 lines · 0 tokens per session scan A 84ed5c26ffe1

Subscribe to this mod's changes

CLAUDE is an agent published in the GitHub repository serpin-taxt/openchief (24 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,312 tokens. 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.

Related

Other agents, from other repositories

ecto-schema-designer

Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.

oliver-kriska/claude-elixir-phoenix · 30 tokens

database-architect

Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.

softspark/ai-toolkit · 67 tokens

db2-dba

DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…

josstei/maestro-orchestrate · 303 tokens

data-architect

Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.

SenolIsci/mykg · 59 tokens

rest-endpoints

The small, stable slice of the REST API that guides depend on, alongside the primary MCP surface.

TAJD/projektor · 20 tokens

builder

Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…

chmonitor/chmonitor · 0 tokens