Borrowing it
Nothing to install: this file belongs to patriceckhart/hrdx. 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/patriceckhart/hrdx/main/AGENTS.mdgit clone --depth 1 https://github.com/patriceckhart/hrdxWrote 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/patriceckhart/hrdx/agents-md)<a href="https://agentmods.dev/instructions/patriceckhart/hrdx/agents-md"><img src="https://agentmods.dev/badge/instructions/patriceckhart/hrdx/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/patriceckhart/hrdx/agents-md"><img src="https://agentmods.dev/badge/instructions/patriceckhart/hrdx/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.02474 | $0.02474 |
| Opus 5 | $0.01237 | $0.01237 |
| Sonnet 5 | $0.00495 | $0.00495 |
| Haiku 4.5 | $0.00247 | $0.00247 |
Grade A, and why
hrdx 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 5d 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working Agreement for hrdx
This file defines how automated coding assistants should work in this repository. Treat it as a practical operating manual, not a substitute for reading the code.
Product intent
hrdx is an experimental, minimal, lightweight terminal multiplexer for coding agents and shells. Changes should preserve its defining properties:
- one portable Go binary
- every pane backed by a real PTY
- projects represented as workspaces with tabs and split layouts
- terminal behavior compatible with ordinary agent TUIs and shells
- persistent sessions through a lightweight holder process
- predictable behavior on macOS, Linux, and Windows
- a small dependency and operational footprint
Prefer a narrow, explicit implementation over a generalized subsystem. New abstractions must earn their cost through a real ownership boundary or repeated use.
Starting a task
Build context before editing:
- Inspect
git status --short --branch. Existing modifications may belong to the user or another agent. - Locate and read every
AGENTS.mdthat governs the target path. - Read the owning implementation, nearby tests, and user-facing documentation for the behavior.
- Reproduce reported failures when feasible. Keep expected behavior distinct from observed behavior.
- For GitHub work, inspect the issue, discussion, or pull request before implementing it. Do not change branches merely to review a pull request.
Do not use one search result or one function as a complete model of a feature. Follow the path through UI state, terminal or holder behavior, persistence, API representations, tests, and platform-specific files where relevant.
Code ownership map
Put behavior in the package that owns the concern:
| Area | Responsibility |
|---|---|
cmd/hrdx |
CLI flags, configuration assembly, startup, process modes, and platform wiring |
internal/api |
Socket server, newline-delimited JSON protocol, public request and response types, subscriptions |
internal/holder |
Persistent PTY ownership, attach and detach, replay ring, holder protocol |
internal/state |
Serializable workspaces, tabs, panes, layouts, and preferences |
internal/term |
PTY pane lifecycle, input encoding, resize, scrollback, selection, terminal-facing helpers |
internal/ui |
Bubble Tea model, rendering, layout, input, menus, settings, persistence coordination, API handling |
internal/vt |
Escape parsing, terminal state, glyphs, colors, history, and screen model |
internal/update |
Update checks and self-update |
internal/winproc |
Windows foreground-process and process-tree behavior |
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.
- 5d ago First seen · 228 lines · 2,474 tokens per session scan A c2187cf7b988
hrdx AGENTS.md is an instructions file published in the GitHub repository patriceckhart/hrdx (48 stars, last pushed 4d ago), licensed MIT. It adds 2,474 tokens to every session, about $0.0124 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-09-03.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.