Borrowing it
Nothing to install: this file belongs to senna-lang/herdr-agent-usage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/senna-lang/herdr-agent-usage/main/AGENTS.mdgit clone --depth 1 https://github.com/senna-lang/herdr-agent-usageWrote 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/senna-lang/herdr-agent-usage/agents-md)<a href="https://agentmods.dev/instructions/senna-lang/herdr-agent-usage/agents-md"><img src="https://agentmods.dev/badge/instructions/senna-lang/herdr-agent-usage/agents-md/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/instructions/senna-lang/herdr-agent-usage/agents-md"><img src="https://agentmods.dev/badge/instructions/senna-lang/herdr-agent-usage/agents-md.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.00784 | $0.00784 |
| Opus 5.5 | $0.00314 | $0.00314 |
| Sonnet 5.5 | $0.00157 | $0.00157 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
herdr-agent-usage 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 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions
Scope
These instructions apply to the entire repository. Treat the rules below as architectural constraints, not preferences.
Provider Extensibility
- The set of providers is open-ended. Assume that providers will be added, removed, or changed.
- Provider-neutral code MUST NOT depend on the current provider count or duplicate the provider list outside the canonical registry.
- A provider implementation MUST conform to the shared provider contracts and register through the same mechanism as every other provider.
- Provider-specific code MAY translate authentication, session, transcript, model, or API formats into shared domain types. It MUST NOT redefine shared domain behavior.
Provider Symmetry
- Shared code MUST interact with every provider through the same provider-neutral contracts.
- Shared code MUST operate on common domain types rather than branch on provider names, model names, or vendor-specific types.
- No provider may receive a privileged path through shared layers. A change of provider must change the adapter and its data, not the surrounding architecture.
- If a requirement applies across providers, add it to the shared contract. If it exists only because of an external provider format or capability, contain it within that provider's adapter.
- Provider adapters may differ internally only where their external systems differ. Those differences MUST end at the adapter boundary.
Directory and Package Boundaries
- Treat each directory as an architectural module and preserve the repository's dependency direction.
- This repository is written in Go. A package's exported identifiers are its public API; unexported identifiers are implementation details. Consumers MUST depend on the package API rather than another package's implementation details.
- Provider packages MUST NOT import one another. Behavior shared by multiple providers belongs in a provider-neutral package at the appropriate dependency layer.
- The Go
internalvisibility boundary and every lint rule configured in.golangci.ymlare mandatory. - Do not bypass a boundary with deep imports, duplicate implementations, or convenience dependencies. If the desired dependency violates the graph, move the shared abstraction to the correct layer instead.
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 · 59 lines · 784 tokens per session scan A 887858de4c4d
herdr-agent-usage AGENTS.md is an instructions file published in the GitHub repository senna-lang/herdr-agent-usage (62 stars, last pushed 3d ago), licensed MIT. It adds 784 tokens to every session, about $0.0031 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.