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/am-will/limux/agents-mdgit clone --depth 1 https://github.com/am-will/limuxWhat 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.01208 | $0.01208 |
| Opus 5 | $0.00604 | $0.00604 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
limux 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Limux contributor guide
This file is for agents editing the Limux source tree. Do not confuse it with
the AGENTS.md generated by limux agent-team inside a user's shared cwd;
that generated file documents the runtime agent message protocol.
What Limux Is
Limux is a GTK4 + libadwaita terminal workspace manager for Linux. Terminal
rendering is embedded Ghostty (libghostty.so), and external automation drives
the running app through a Unix socket and the limux-cli crate.
Crates
| Crate | Role |
|---|---|
limux-protocol |
JSON request/response envelope types. |
limux-core |
In-process command dispatcher and state engine. Core IDs are u64. |
limux-control |
Unix socket path, auth, framing, and standalone control server. |
limux-ghostty-sys |
Raw FFI bindings to ghostty/include/ghostty.h. |
limux-host-linux |
GTK host binary, window/pane/tab UI, terminal integration, live control bridge. |
limux-cli |
User-facing CLI and agent integration commands. |
Binaries
Local debug builds produce two important binaries:
target/debug/limuxis the GTK host fromlimux-host-linux; it only accepts GTK/GApplication flags.target/debug/limux-cliis the CLI; use this for subcommands such asidentify,agent-team,notify,read-screen, andsend.
Installed packages expose limux as the CLI. Running installed limux with no
arguments launches the private host binary (limux-host) from libexec.
cargo build -p limux-cli --bin limux-cli
./target/debug/limux-cli --help
Quality Gate
The canonical check is:
./scripts/check.sh
It runs cargo fmt --check,
cargo clippy --workspace --all-targets -- -D warnings, and
cargo test --workspace. Run narrower checks while iterating:
cargo check -p limux-host-linux
cargo test -p limux-cli
cargo check --workspace
For live agent/control-socket behavior, prefer the maintained smoke harness:
./scripts/xvfb-smoke-test.sh
LIMUX_SMOKE_PROFILE=debug ./scripts/xvfb-smoke-test.sh
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 · 139 lines · 1,208 tokens per session scan A 6b134e1f87bd
limux AGENTS.md is an instructions file published in the GitHub repository am-will/limux (546 stars, last pushed 3d ago), licensed MIT. It adds 1,208 tokens to every session, about $0.0060 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
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).
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.
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.