hird AGENTS.md

Repository instructions for AI coding agents working on hird, including its Rust workspace rules and definition of done. A Rust workspace is a repository that groups multiple Rust packages together.

In plain words
What is it for?
They are for guiding hird changes, including formatting with cargo fmt, linting with cargo clippy, documenting public APIs, and updating tests when behavior changes.
Why use it?
They give the agent project-specific standards for implementing tickets and deciding when a change is complete.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/no-materials/hird/agents-md
Clone the repo
git clone --depth 1 https://github.com/no-materials/hird

Made for: Codex, OpenCode.

Per session 1,662 This file is loaded in full into every session.
When invoked 1,662 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01662 $0.01662
Opus 5 $0.00831 $0.00831
Sonnet 5 $0.00332 $0.00332
Haiku 4.5 $0.00166 $0.00166

Measured yesterday against content hash 76fb80e0805f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

hird 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 yesterday.

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.

AGENTS.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This repository is maintained with help from AI coding agents (e.g. Codex/ChatGPT/Claude). This file defines how to make changes, what “done” means, and the project defaults we enforce.

North Star

  • Keep core crates small, predictable, and long-lived.
  • Prefer simple, explicit designs over clever ones.
  • Avoid dependency creep; keep compile times and surface area under control.
  • Optimize for long-term architecture over short-term compatibility; it’s OK to break callers to get the right core shape.

Non-negotiables (Definition of Done)

  • cargo fmt passes.
  • cargo clippy passes (-D warnings).
  • Public APIs are documented (types/functions; public fields/variants where it matters).
  • Tests updated/added when behavior changes.
  • Examples/benchmarks live in separate top-level workspace crates (no extra dev-deps in core crates).
  • Never reference tickets, ADRs, plans, phases, or agent sessions in code, comments, docstrings, or commit messages. These are project-management artifacts that rot. Code should justify itself; context belongs in the commit message or PR description, not in the source tree.

Suggested commands:

cargo fmt --all
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features

Before implementing a ticket

Before writing any code, read these files in order:

  1. The assigned issue (bd show <id>).
  2. DECISIONS.md — locked architecture constraints you must not violate.
  3. phrasebook.md — canonical surface syntax conventions.
  4. The parent epic ticket if one exists (for broader context and out-of-scope boundaries).

Rust workspace expectations

  • MSRV is set in Cargo.toml (rust-version, currently 1.97); keep it compatible.
  • Follow workspace lint policy (notably: unsafe_code = "deny" and missing_docs = "warn").

no_std policy (core crates)

  • Default assumption for foundational crates: #![no_std] whenever practical (use extern crate alloc when needed).
  • Keep std behind an explicit std feature flag when required.
  • Avoid std collections in no_std crates; use hashbrown (and alloc types) instead.

Read the full file on GitHub · 161 lines

Changes

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.

  1. yesterday First seen · 161 lines · 1,662 tokens per session scan A 76fb80e0805f

Subscribe to this mod's changes

hird AGENTS.md is an instructions file published in the GitHub repository no-materials/hird (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,662 tokens to every session, about $0.0083 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.