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.
npx agentmods add agents/gammalabtechnologies/harmonist/schemagit clone --depth 1 https://github.com/GammaLabTechnologies/harmonistWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.04818 |
| Opus 5 | $0.00000 | $0.02409 |
| Sonnet 5 | $0.00000 | $0.00964 |
| Haiku 4.5 | $0.00000 | $0.00482 |
Grade A, and why
SCHEMA 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.
How it starts
The opening of the file, as written. The whole thing — 459 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Schema v2
Single source of truth for the shape of every agent in this pack. One schema, one pool —
agents/index.jsonis generated from these files, and the orchestrator routes tasks to agents via that index.See also:
agents/STYLE.md— how the body of an agent should read (mission shape, critical rules, Deep Reference convention, retrofit checklist). SCHEMA enforces the frontmatter contract; STYLE shapes the prose.
File layout
Every agent lives at agents/<category>/<slug>.md and has three parts:
---
<YAML frontmatter — required fields + optional fields>
---
<Markdown body — the agent's system prompt>
Anything under agents/ that is not an agent file (README, SCHEMA, index.json,
playbooks, templates, scripts) MUST NOT start with --- as its first line.
The linter uses the first-line --- check to discriminate.
Frontmatter — required
Every field below is mandatory. Missing any → lint error.
| Field | Type | Values | Meaning |
|---|---|---|---|
schema_version |
enum (string) | currently "2" |
Declares which version of this schema the file conforms to. Linter rejects unknown / outdated versions; scripts/migrate_schema.py rolls older versions forward automatically. See the "Schema versioning" section at the bottom of this doc. |
name |
string | human-readable display name | Shown in integrations, UI surfaces, and the agent's self-reference in the body. May be kebab-case (e.g. qa-verifier for strict reviewers) or human-formatted (e.g. Backend Architect, DevOps Automator for persona agents). Does NOT have to match the filename. The identity key used for routing, state, and hooks is the slug — see below. |
description |
string | 1–2 sentences | What it does, when to invoke it. Used by the orchestrator for routing. |
category |
enum | see list below | Top-level bucket. Must match the parent directory. |
protocol |
enum | strict | persona |
How the agent behaves (see "Protocol" section). |
readonly |
bool | true | false |
true = reviewer/scout, cannot edit files. false = write agent. |
is_background |
bool | true | false |
true = long-running (tests, lint, builds). Default false. |
model |
string | a Cursor model slug, e.g. claude-opus-4-8 |
Concrete model the dispatched subagent runs on. Defaults to the strongest model. See "Model" below. |
tags |
list[string] | lowercase kebab | Searchable labels used by index.json for task-to-agent matching. |
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.
- 3d ago First seen · 459 lines · 0 tokens per session scan A 5b70060eea39
SCHEMA is an agent published in the GitHub repository GammaLabTechnologies/harmonist (2,254 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,818 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.
Other agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
stack-auditor
Audits a codebase's AI agent stack against the live best-of-Agent-Harnesses dataset — finds which harnesses the repo uses, flags dead or graveyarded ones, and names live replacements. Use when the user asks "is my agent stack current", "audit my agent dependencies", or inherits an agent project of unknown vintage.
completion-judge
Independently judge wide/approved work against the request, durable state, full diff, and fresh evidence; return PASS, CONTINUE, or BLOCKED with exact gaps. Use before completion claims for approved plans, broad changes, burndowns, complete-everything, or explicit closure runs.