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/wasix-org/wasinix/agents-mdgit clone --depth 1 https://github.com/wasix-org/wasinixWrote 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/wasix-org/wasinix/agents-md)<a href="https://agentmods.dev/instructions/wasix-org/wasinix/agents-md"><img src="https://agentmods.dev/badge/instructions/wasix-org/wasinix/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.01987 | $0.01987 |
| Opus 5 | $0.00993 | $0.00993 |
| Sonnet 5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
wasinix 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 4d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repo as an agent
Before your first edit, read docs/style.md and docs/building.md in full,
plus the row below covering whatever you are about to touch. This file is an
index and does not repeat what it links to. Skipping one of those docs does not
exempt you from what it says.
AGENTS.md contains only guidance specific to agents and not owned by one
topic. Put guidance that applies to humans and agents in the relevant general
doc:
| Read | For |
|---|---|
CONTRIBUTING.md |
contribution and PR expectations |
docs/setup.md |
first-time setup and wasinix doctor |
docs/architecture.md |
how the layers fit together, flake outputs, one place per concern |
docs/c.md |
C/C++ toolchain, profiles, and cross stdenv |
docs/packaging.md |
adding a package, tweaks, deps, patches, tests |
docs/registry.md |
publishing, version history, rels, PR previews |
docs/rust.md |
rust builds, crate patches, the cargo registry |
docs/python.md |
CPython, package overlays, and wheels |
docs/building.md |
where builds run, building one thing, checking work |
docs/ci.md |
the orchestrator, its command tree, and the run model |
docs/style.md |
comments, naming, commits, fail loud, root cause |
docs/updating.md |
the pin updater and updateNotes |
docs/spot.md |
experimenting without rebuilding the world |
Do not restate those rules here. Add a ## For agents section to the owning doc
only when the agent workflow genuinely differs from the human workflow.
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.
- 4d ago First seen · 160 lines · 1,987 tokens per session scan A 2290bf312f8c
wasinix AGENTS.md is an instructions file published in the GitHub repository wasix-org/wasinix (5 stars, last pushed 6d ago), licensed MIT. It adds 1,987 tokens to every session, about $0.0099 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.
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.