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/nulang-org/nulang/agents-mdgit clone --depth 1 https://github.com/nulang-org/nulangWrote 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/nulang-org/nulang/agents-md)<a href="https://agentmods.dev/instructions/nulang-org/nulang/agents-md"><img src="https://agentmods.dev/badge/instructions/nulang-org/nulang/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.1 | $0.11479 | $0.11479 |
| Opus 5 | $0.05740 | $0.05740 |
| Sonnet 5 | $0.02296 | $0.02296 |
| Haiku 4.5 | $0.01148 | $0.01148 |
Grade A, and why
nulang 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 6d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Practical orientation for AI assistants working in the Nulang codebase. All paths are relative to the repo root (
~/nulang).
Project Overview
Nulang is a distributed, actor-based programming language written in Rust (edition 2021, Cargo workspace with a primary nulang crate and a nulang-ai support crate). It fuses Erlang-style fault-tolerant actors with a Rust/Pony-inspired type system (Hindley-Milner inference + reference capabilities + row-polymorphic algebraic effects), a register-based bytecode VM, a Cranelift JIT, a WASM backend (MIR→WASM via wasm-encoder) with a Wasmtime host runtime, BEAM/OTP primitives, CRDTs, location-transparent distribution, libsql/Turso persistence, PyO3 Python interop, a C-compatible FFI layer, a v0.9 AI runtime (pure types in crates/nulang-ai/, Runtime glue in src/runtime/), and a format-stability layer (src/format/ — frozen .nbc bytecode artifacts, NUL0 wire protocol versioning, migration registry). Status: Alpha; 1558 tests pass in the core crate (cargo test), 1596 with --features wasm-backend; the nulang-ai crate ships 58 additional tests (cargo test -p nulang-ai). License: Apache-2.0.
Architecture & Data Flow
The compiler pipeline has two backends, selectable via --backend:
Bytecode backend (default):
source &str
-> Lexer::lex() -> Vec<Token> src/lexer.rs
-> Parser::parse_module() -> AstModule src/parser.rs
-> TypeChecker::check_module() -> Type src/typechecker.rs (HM Algorithm W)
-> EffectChecker::check_module() -> () src/effect_checker.rs
-> CapabilityAnalyzer::infer_cap() -> Capability src/effect_checker.rs
-> HIR lowering (hir_lower::lower_module) -> HIR Module src/hir_lower.rs
-> MIR lowering (mir_lower::lower_module) -> MIR Module src/mir_lower.rs
-> MIR codegen (mir_codegen::compile_mir) -> CodeModule src/mir_codegen.rs
-> VM::load_module() + VM::run() -> Value src/vm.rs (register VM + JIT tiering)
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.
- 6d ago First seen · 189 lines · 11,479 tokens per session scan A 802630840367
nulang AGENTS.md is an instructions file published in the GitHub repository nulang-org/nulang (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 11,479 tokens to every session, about $0.0574 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
turso AGENTS.md
AGENTS.md instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
ton-rs AGENTS.md
AGENTS.md instructions for ston-fi/ton-rs, covering ton-rs agent guide, repository, boundaries, public api and ton invariants.
rlm-rs copilot-instructions.md
Copilot instructions for zircote/rlm-rs, covering github copilot instructions, project context, code generation guidelines, error handling and type annotations.
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.