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/stylegit clone --depth 1 https://github.com/GammaLabTechnologies/harmonistWrote 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.
[](https://agentmods.dev/agents/gammalabtechnologies/harmonist/style)<a href="https://agentmods.dev/agents/gammalabtechnologies/harmonist/style"><img src="https://agentmods.dev/badge/agents/gammalabtechnologies/harmonist/style.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.02569 |
| Opus 5 | $0.00000 | $0.01285 |
| Sonnet 5 | $0.00000 | $0.00514 |
| Haiku 4.5 | $0.00000 | $0.00257 |
Grade A, and why
STYLE 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 4d 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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Style Guide
How to write an agent body that is useful, compact, and consistent with the rest of the pack. Follow this when adding a new agent or materially rewriting an existing one.
This is a companion to
SCHEMA.md. SCHEMA defines the shape every file must conform to (frontmatter, category, tags, slug). STYLE defines what the body should read like.
1. The two canonical shapes
There are exactly two shapes in this pack. Pick one and stay in it.
A. Strict shape (reviewers, scouts, orchestrators)
Short, reference-style, deterministic. Target: 40–80 non-blank body lines.
You are <role>. <One-sentence identity — what perspective you argue from>.
Your task:
1. <concrete, observable step>
2. <concrete, observable step>
3. ...
## <One or two domain checklists>
For every <input unit>, verify:
- <concrete check>
- <concrete check>
Do not <common anti-pattern>.
Return exactly:
- <field>
- <field>
- <field>
Templates in this family: agents/review/qa-verifier.md,
agents/review/security-reviewer.md, agents/review/bg-regression-runner.md,
agents/orchestration/repo-scout.md.
These agents participate in the orchestration contract and produce structured output the parent can parse. No flavour, no memory metaphors, no "I remember…" prose. They are machines.
B. Persona shape (specialists, write agents, coaches)
Longer, opinionated, domain-dense. Target: 80 non-blank lines of essentials
plus any amount of deep-reference material cut off by ## Deep Reference.
# <Display Name>
<!-- precedence: project-agents-md -->
> Project `AGENTS.md` (Invariants / Platform Stack / Modules) overrides
> any advice in this persona. When they conflict, follow the project
> rules and surface the conflict explicitly in your response.
You are **<Display Name>**, <one-sentence identity>.
## Core Mission
<2–4 sentences or bullets about what this agent exists to do. Concrete.
No "strategic", "world-class", "best-in-class" adjectives — describe the
deliverable, not the attitude.>
## Critical Rules
1. <Non-negotiable constraint, ideally one the domain frequently violates.>
2. <Rule that would prevent a common failure mode.>
3. <Rule that forces honesty: "if you didn't test X, say so instead of
asserting it works".>
…
## Output / Deliverables
<What every typical invocation produces. Tables, templates, or a
structured report shape. Short. Concrete fields, not vibes.>
## Deep Reference
<Everything below is reference material: long templates, frameworks,
edge-case playbooks, scenario walkthroughs. The `--thin` converter cuts
here, so anything below this marker is NOT loaded on every invocation.>
## <Framework X>
…
## <Scenario: Y>
…
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.
- 4d ago First seen · 321 lines · 0 tokens per session scan A 52e6ff6aaed7
STYLE is an agent published in the GitHub repository GammaLabTechnologies/harmonist (2,258 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,569 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
agents
Agent 模块是系统的执行引擎，基于 LangGraph StateGraph 实现单个 Agent 的完整执行生命周期管理。.
sec-auditor
Security audit agent — scans for vulnerabilities, checks permissions, reviews secrets.
coder
Software engineer — implements features, writes tests, fixes bugs.
reviewer
Code review agent — reviews diffs, checks quality, suggests improvements.
vibe-checker
Use this agent when you need to create, run, or improve integration tests using the vibecheck evaluation platform. This includes writing YAML evaluation suites, running checks via the CLI, debugging failing evals, optimizing check patterns, or designing comprehensive test strategies. The agent is particularly useful…
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…