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/soolaxx/swarmux/agents-mdgit clone --depth 1 https://github.com/soolaxx/swarmuxWrote 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/soolaxx/swarmux/agents-md)<a href="https://agentmods.dev/instructions/soolaxx/swarmux/agents-md"><img src="https://agentmods.dev/badge/instructions/soolaxx/swarmux/agents-md.svg" alt="Measured on agentmods" 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 | $0.00346 | $0.00346 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
swarmux 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 3d 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.
This is a copy
100% identical to swarmux AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Agent Instructions
All CLI implementation and CLI UX decisions in this repo must follow these rules:
- JSON-first contract
- Every command must support machine-readable output.
- Prefer JSON as the default for agent-facing paths.
- Human-friendly text output is secondary and must not change machine semantics.
- Deterministic interfaces
- Keep flags, field names, and output shapes stable.
- Avoid ambiguous parsing and context-dependent behavior.
- Treat CLI output as an API contract.
- Non-interactive by default
- No prompts for normal execution paths.
- No hidden defaults that require human interpretation.
- Everything required for execution must be explicit in flags or JSON payloads.
- Separation of data and presentation
- Do not encode presentation-only strings into machine fields.
- Keep structured data in structured fields; render formatting only in text mode.
- Script/agent safety
- Commands should be composable, predictable, and idempotent where possible.
- Provide clear exit codes and actionable errors.
- Prefer explicit validation errors over silent coercion.
- Verb-based task model
- Use clear, action-oriented subcommands (
submit,start,show, etc.). - Keep command behavior narrow and single-purpose.
- Validation and simulation
- Validate inputs defensively (agents hallucinate malformed values).
- Support dry-run/preview for mutating operations whenever feasible.
- Runtime semantics
tuiis a first-class runtime besideheadlessandmirrored.- Runtime controls task/session execution only. Popup/window presentation belongs in tmux bindings or operator workflow, not in the core CLI contract.
If there is a conflict with existing CLI patterns, align with this rule set.
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.
- 3d ago First seen · 42 lines · 346 tokens per session scan A 0390c4cc9a5d
swarmux AGENTS.md is an instructions file published in the GitHub repository soolaxx/swarmux (1 stars, last pushed 4d ago), licensed MIT. It adds 346 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to swarmux AGENTS.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
kleosrules AGENTS.md
Instructions for kleosr/kleosrules, a project described as: Cursor harness pack: user rules, skills, Bash hooks, local HANDOFF memory. macOS, Linux, Windows (WSL).
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.