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 instructions/farol-team/gnap/claude-mdgit clone --depth 1 https://github.com/farol-team/gnapWrote 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/instructions/farol-team/gnap/claude-md)<a href="https://agentmods.dev/instructions/farol-team/gnap/claude-md"><img src="https://agentmods.dev/badge/instructions/farol-team/gnap/claude-md.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.00564 | $0.00564 |
| Opus 5 | $0.00282 | $0.00282 |
| Sonnet 5 | $0.00113 | $0.00113 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
gnap CLAUDE.md 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Repo Is
GNAP (Git-Native Agent Protocol) — a specification for coordinating AI agent teams using git as the only transport/storage layer. No server required.
Status: Draft v4, March 2026. This is a protocol spec repo, not a traditional software project.
Architecture
AgentHQ (Application Layer) — budgets, dashboards, workflows (separate repo)
GNAP (Protocol Layer) — 4 entities: Agent, Task, Run, Message
Git (Transport) — push/pull/commit = the message bus
Protocol (GNAP core): Defined in README.md. Four JSON entities live in .gnap/ — agents.json, tasks/*.json, runs/*.json, messages/*.json. Protocol version in .gnap/version.
Key Files
| File | Purpose |
|---|---|
README.md |
GNAP protocol spec — the 4 entities, schemas, state machines, transport, onboarding |
ONBOARDING.md |
Detailed step-by-step agent onboarding guide |
CONTRIBUTING.md |
Contribution guidelines |
examples/.gnap/ |
Reference data: agents.json, tasks/, runs/, messages/, version |
docs/gnap-overview.svg |
Visual diagram embedded in README hero section |
Core Protocol Concepts
Task states: backlog → ready → in_progress → review → done (also blocked, cancelled). Reverse transitions: review → in_progress (reject), blocked → ready (unblocked).
Commit convention: <agent-id>: <action> <entity> [details] — git history IS the audit log.
Heartbeat loop: Each agent polls on heartbeat_sec interval (default 300s): pull → check status → check tasks → check messages → work → commit → push.
Conflict resolution: git merge/rebase. On conflict: pull + rebase + retry push (max 3).
Editing Guidelines
- This is a spec repo. Changes to
README.mdchange the protocol definition. - JSON schemas in the spec docs are normative — keep entity examples consistent across all docs.
- The four GNAP entities (Agent, Task, Run, Message) are intentionally minimal. Resist adding new protocol-level entities.
examples/should always be valid instances of the schemas defined in the spec.- Operational concerns (budget enforcement, stall detection, concurrency control) belong in AgentHQ, not the protocol.
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 · 48 lines · 564 tokens per session scan A a0854540c320
gnap CLAUDE.md is an instructions file published in the GitHub repository farol-team/gnap (83 stars, last pushed 5mo ago), licensed MIT. It adds 564 tokens to every session, about $0.0028 per session on Opus 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 instructions, from other repositories
pi-agent-dashboard AGENTS.md
AGENTS.md instructions for BlackBeltTechnology/pi-agent-dashboard, covering pi dashboard, docs-first gate — kb before grep (per-turn doctrine), code instructions (per-turn doctrine), investigation protocol — index first and documentation update protocol.
mcp-devtools CLAUDE.md
Claude Code instructions for sammcj/mcp-devtools, covering claude.md, commands, build and run, testing and code quality.
goal-flight AGENTS.md
AGENTS.md instructions for simonrowland/goal-flight, covering agent notes, goal flight routing, project commands (this repo), git workflow (this repo) and git-visible trigger hygiene.
goal-flight CLAUDE.md
Claude Code instructions for simonrowland/goal-flight, covering claude code notes and git-visible trigger hygiene.
growmos AGENTS.md
Instructions for codician-team/growmos: This repository keeps a knowledge graph in .growmos/ (entities, typed relations, provenance, profiles, a journal). It is the shared world model that survives context windows. Treat it as memory you read at the start of work and write to as you develop. Zero-config commands.
akidevrule CLAUDE.md
Instructions for lacvietanh/akidevrule, covering akidevrule, project role, source of truth, file naming conventions and rule authoring principles.