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/ricktaylor/hardy/agents-mdgit clone --depth 1 https://github.com/ricktaylor/hardyWhat 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.01861 | $0.01861 |
| Opus 5 | $0.00931 | $0.00931 |
| Sonnet 5 | $0.00372 | $0.00372 |
| Haiku 4.5 | $0.00186 | $0.00186 |
Grade A, and why
hardy 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hardy — agent guide
Hardy is a performant, RFC 9171-compliant, extensible BPv7 Delay-Tolerant Networking (DTN) implementation, written in async Rust. It is a Cargo workspace on the stable toolchain; the edition and MSRV are defined in the workspace Cargo.toml ([workspace.package]). See README.md for the full feature list and the complete crate inventory.
Workspace layout
The workspace is split into many small crates. The ones you will touch most often:
cbor/— RFC 8949 canonical CBOR codec (no_std).bpv7/— RFC 9171 bundle format: parsing, building, editing, BPSec (no_std).bpa/— the Bundle Processing Agent library: routing, dispatch, filter pipeline, RIB, storage/CLA/service registries.bpa-server/— the binary that wires the BPA together; closed-source extensions register against the unmodifiedbpacrate via public traits.eid-patterns/,async/,proto/,otel/— supporting libraries.*-storage/— pluggable storage backends (localdisk, sqlite, postgres, s3).tcpclv4/,file-cla/,bibe/— convergence layers;tvr/— Time-Variant Routing agent.tools/,bpv7/tools/,cbor/tools/— CLI tools (bp,bundle,cbor).
tests/interop/mtcp is excluded from the workspace and built separately.
Build, test, lint
Proto-dependent crates require protoc (CI installs protobuf-compiler). Common commands:
cargo build --release # build everything
cargo test --workspace --all-features # run the test suite
cargo fmt # format
cargo clippy --all-targets --all-features # lint
A change is not done until these CI gates pass — run them before handing work back:
cargo fmt --check
cargo clippy --locked --all-targets --all-features -- -D warnings
cargo test --locked --all-features --workspace
Clippy is enforced with -D warnings: no warnings are allowed to land.
Code style — the essentials
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 · 85 lines · 1,861 tokens per session scan A 1d5f6565e5bd
hardy AGENTS.md is an instructions file published in the GitHub repository ricktaylor/hardy (23 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,861 tokens to every session, about $0.0093 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.