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/sympozium-ai/celln/agents-mdgit clone --depth 1 https://github.com/sympozium-ai/cellnWrote 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/sympozium-ai/celln/agents-md)<a href="https://agentmods.dev/instructions/sympozium-ai/celln/agents-md"><img src="https://agentmods.dev/badge/instructions/sympozium-ai/celln/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.00770 | $0.00770 |
| Opus 5 | $0.00385 | $0.00385 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
celln 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 today.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — house rules
Read this before touching the code. It inherits the constraints and vocabulary
of the design corpus in docs/.
Vocabulary (non-negotiable)
- mote = the substrate at rest (stripped kernel +
pilot). cell = a live, sealed, tool-loaned mote. Every cell is a sealed mote. Never use the two interchangeably. Full glossary:docs/NAMES_AND_CONVENTIONS.md. - Components:
assay(host daemon, where the distro lives),warden(per-cell VMM),pilot(in-cell supervisor). 1 warden : 1 microVM : 1 cell.
Constraints (from the build plan §1)
- The guest never boots in the hot path — spawn is a CoW fork of a warm mote.
- No in-kernel network stack;
pilot-fetchsends bounded HTTPS requests over four dedicated PIO ports (0x500-0x503) to the host proxy. - The filesystem has no authority to run code — exec is by content hash against a signed manifest.
- Tool code is unwritable from the guest side (stage-2 sealing).
- Authority only shrinks — the ratchet is host-enforced in
warden. - Compatibility is a feature — every ABI break is a silent latency tax.
Working rules
- Never fake a hardware guarantee. If a backend can't provide a property,
return
Unsupported(seewarden::vmm::kvm). A stub that lies is worse than a stub that refuses. - Prefer measurement over assertion. Performance claims become committed numbers, not comments.
- Reduce guest attack surface and stay reversible when choosing between implementations; keep the rationale close to the code it affects.
- Rust for code, Make for orchestration, shell for glue. No Python.
make cimust stay green:fmt-check build test.
Where things are
- Trust core (no I/O):
crates/celln-manifest - Store:
crates/celln-store - Cell spec parsing + validation:
crates/celln-spec - Grading, tiered resolution + CLI:
crates/celln-assay - Build plane (rebuild + reproduce):
crates/celln-forge - The
cellnCLI users actually run:crates/celln-cli - Ratchet + VMM trait/backends:
crates/celln-warden(vmm/kvm.rsreal KVM,vmm/boot.rsstock-kernel boot) - Exec gate + lanes + explain + demos:
crates/celln-pilot - Guest-side code:
guest/init/init.c(freestanding, no libc); guest images built byscripts/mkinitramfs.shandscripts/mktoolfs.sh - Hardware checks:
celln verify; measurements:make bench-kvm(local output undertarget/celln-bench/)
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.
- today Changed · +1 lines · +19 tokens per session 2425b1f143f6
- 6d ago First seen · 58 lines · 751 tokens per session scan A 0d239d7a2ff8
celln AGENTS.md is an instructions file published in the GitHub repository sympozium-ai/celln (53 stars, last pushed yesterday), licensed Apache-2.0. It adds 770 tokens to every session, about $0.0038 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.
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.
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).