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/kampe/herdforge/agents-mdgit clone --depth 1 https://github.com/Kampe/HerdforgeWhat 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.02630 | $0.02630 |
| Opus 5 | $0.01315 | $0.01315 |
| Sonnet 5 | $0.00526 | $0.00526 |
| Haiku 4.5 | $0.00263 | $0.00263 |
Grade A, and why
Herdforge AGENTS.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 2d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Herdforge Agentic Worker Contract
This contract governs all AI agents (Claude, Codex, Grok, AGY, and OpenCode) participating in the Herdforge software factory fleet.
1. Core Engineering Invariants & Rules
-
Fleet-Only Forging (FAC-113, hard invariant):
- Herdforge forges itself with its own Herdr fleet (configured vendor harnesses in Herdr tabs, driven by
herd dispatch/herd send/herd review). This is the entire point of the repo: the product must be exercised on itself. - NEVER use Claude subagents (the Agent tool: general-purpose, Explore, etc.) to build, fix, review, or audit anything in this repo. Using them defeats the dogfooding premise and stops testing the actual system.
- The coordinator dispatches to the fleet and owns git plumbing (harvest → PR → merge →
herd approve). Fleet agents commit in their worktree and report; they never push or merge. When an agent stalls, the fix is a firmer packet /herd kick/ the completion self-gate (herd verify), never routing around the fleet.
- Herdforge forges itself with its own Herdr fleet (configured vendor harnesses in Herdr tabs, driven by
-
Fail-Closed Execution:
- All CLI tools and internal package functions must propagate non-zero exit codes on error (
os.Exit(1)or non-nilerror). - HTTP responses carrying
{"error": ...}JSON bodies returned under200 OKmust be rejected as hard errors.
- All CLI tools and internal package functions must propagate non-zero exit codes on error (
-
Mutation & Test Non-Vacuity Discipline:
- Never write a test that passes vacuously.
- Any negative assertion guard must be manually or programmatically verified failing against an introduced regression before PR approval.
-
Repo-Relative Path Enforcement:
- Never output absolute file paths (e.g.
/Users/...or/tmp/...) inside configuration files, git hooks, or generated artifacts. - Use
./or runtime environment variables ($HERD_ROOT,$HERD_WORKTREE) to ensure worktree portability.
- Never output absolute file paths (e.g.
-
Deterministic Task Selection:
- When listing candidate tasks from Kaneo, GitHub, Linear, Jira, or Azure DevOps, candidate arrays must be sorted deterministically: $$\text{Sort Order} = (\text{Priority DESC}, \text{Ticket Number ASC})$$
- Agents must check that role labels match their assigned persona (
pulse --role <role>) before claiming work.
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.
- 2d ago First seen · 140 lines · 2,630 tokens per session scan A 3f6a4996b2b4
Herdforge AGENTS.md is an instructions file published in the GitHub repository Kampe/Herdforge (5 stars, last pushed 2d ago), licensed MIT. It adds 2,630 tokens to every session, about $0.0132 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-31.
Other instructions, from other repositories
ideate AGENTS.md
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.
ideate CLAUDE.md
Instructions for paultyng/ideate, covering claude.md — ideate, what this is, tech stack, project structure and build and run.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
chatgpt-cli CLAUDE.md
Instructions for kardolus/chatgpt-cli, covering chatgpt-cli — release runbook, prerequisites, 1. cut the release, 2. publish the github release + binaries and 3. update the homebrew tap.
klaudiush CLAUDE.md
Instructions for smykla-skalski/klaudiush, covering claude.md, project overview, commands, completion (shell completion scripts) and doctor (diagnose setup and configuration).