Borrowing it
Nothing to install: this file belongs to honeymux/honeymux. 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/honeymux/honeymux/main/AGENTS.mdgit clone --depth 1 https://github.com/honeymux/honeymuxWrote 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/honeymux/honeymux/agents-md)<a href="https://agentmods.dev/instructions/honeymux/honeymux/agents-md"><img src="https://agentmods.dev/badge/instructions/honeymux/honeymux/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/honeymux/honeymux/agents-md"><img src="https://agentmods.dev/badge/instructions/honeymux/honeymux/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.03529 | $0.03529 |
| Opus 5 | $0.01765 | $0.01765 |
| Sonnet 5 | $0.00706 | $0.00706 |
| Haiku 4.5 | $0.00353 | $0.00353 |
Grade A, and why
honeymux 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 9d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents & AI Assistant Notes
Notes for AI assistants working on this codebase.
Code organization
Rule: Prefer modules with one clear responsibility and one primary reason to change. If a file is simultaneously handling transport, parsing, state management, UI coordination, and policy decisions, it is too broad and should be split.
Rule: Keep orchestrator files thin. Managers, hooks, and controllers may coordinate multiple subsystems, but protocol parsing, data normalization, persistence, and boundary-specific policy should live in dedicated helpers or sibling modules.
Rule: Extract trust-boundary logic into explicit boundary modules. Parsing and normalizing untrusted input from sockets, tmux, remotes, config files, or pane output should happen in focused files near the ingress point rather than being inlined throughout higher-level application code.
Rule: When local and remote paths share a concept but differ in transport, separate the shared model from the transport-specific implementation. For example, event parsing, remote transport, permission routing, and UI/session updates should each have their own seam instead of being interleaved in one large file.
Rule: Prefer small reusable primitives for repeated low-level patterns, especially around parsing, buffering, escaping, bounds enforcement, and sanitization. Do not duplicate subtle boundary logic across multiple sockets, streams, or parsers.
Rule: Do not turn util/ into a dumping ground. Only place code there when it is genuinely cross-cutting, domain-agnostic, and likely to be reused by multiple subsystems. Otherwise keep helpers next to the domain that owns them.
Rule: File placement should follow ownership and trust boundaries, not convenience. tmux protocol code belongs with tmux, remote transport code with remote, agent event ingestion with agents, and UI-only transformations with app/components.
Rule: When a refactor extracts a new seam, also improve testability at that seam. New parsers, transports, mappers, and bounded-buffer helpers should usually gain direct unit tests rather than only being covered indirectly through larger integration flows.
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.
- 9d ago First seen · 174 lines · 3,529 tokens per session scan A 19d76bd61015
honeymux AGENTS.md is an instructions file published in the GitHub repository honeymux/honeymux (85 stars, last pushed 3d ago), licensed Apache-2.0. It adds 3,529 tokens to every session, about $0.0176 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
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.