Harmonist is a multi-agent framework for coding assistants that uses hooks to mechanically check required reviews, memory updates, and file supply-chain records before a code-changing turn can finish. It is for teams using tools such as Cursor, Claude Code, Copilot, Windsurf, or Aider to coordinate agents under enforced protocols. The catalogue entries provide agents and rules for Harmonist workflows.
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.
git 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/rules/gammalabtechnologies/harmonist/protocol-enforcement)<a href="https://agentmods.dev/rules/gammalabtechnologies/harmonist/protocol-enforcement"><img src="https://agentmods.dev/badge/rules/gammalabtechnologies/harmonist/protocol-enforcement/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.
<a href="https://agentmods.dev/rules/gammalabtechnologies/harmonist/protocol-enforcement"><img src="https://agentmods.dev/badge/rules/gammalabtechnologies/harmonist/protocol-enforcement.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00570 | $0.00570 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
protocol-enforcement 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Protocol Enforcement
Precedence (when rules conflict)
If two rules give conflicting guidance, resolve in this order:
- Project
AGENTS.md(closest to codebase reality) — wins for architecture, invariants, stack, module boundaries. - This rule (
protocol-enforcement.mdc) — wins for ENFORCEMENT: which agents must be invoked, which hooks must pass, which memory files must be updated. Protocol never negotiates. project-domain-rules.mdc— wins for domain specifics (e.g. financial invariants, game-dev performance budgets). Never overrides enforcement.- Any other
.cursor/rules/*.mdc— wins for stylistic / taste content (naming, formatting, commenting). Never overrides 1–3.
When you follow 2 over 4, say so explicitly in your response.
Enforcement (non-negotiable)
- Your FIRST action must be: read
.cursor/memory/session-handoff.md. - Consult
harmonist/agents/index.jsonto pick agents by tag. Never hard-code agent names; never invent slugs. - NEVER edit code without delegating to the correct subagent. If you edit a file directly, the stop hook will block your turn until a reviewer ran.
- NEVER skip
qa-verifier— run it before claiming done. - NEVER skip
security-reviewerwhen the protocol requires it (auth, secrets, payments, user input, crypto). - When delegating via Task, the FIRST line of the subagent prompt MUST
be
AGENT: <slug>(e.g.AGENT: qa-verifier). Hooks rely on this marker to credit the reviewer. - If you violated the protocol — STOP, tell the user, redo correctly. Do not self-justify.
- Respond to the user in their preferred language.
Escape hatch
For pure Q&A / documentation / planning with zero file writes, the enforcement gate skips itself automatically. You don't need to cite this rule — just answer.
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.
- 1mo ago First seen · 56 lines · 570 tokens per session scan A 19c6bcef3618
protocol-enforcement is a cursor rule published in the GitHub repository GammaLabTechnologies/harmonist (2,254 stars, last pushed 4mo ago), licensed MIT. It adds 570 tokens to every session, about $0.0023 per session on Opus 5.5. 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 cursor rules, from other repositories
agentforge-implementation
Always apply the AgentProdReady architectural implementation workflow.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.