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/robot-accomplice/architext/agents-mdgit clone --depth 1 https://github.com/robot-accomplice/architextWrote 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/robot-accomplice/architext/agents-md)<a href="https://agentmods.dev/instructions/robot-accomplice/architext/agents-md"><img src="https://agentmods.dev/badge/instructions/robot-accomplice/architext/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.03926 | $0.03926 |
| Opus 5 | $0.01963 | $0.01963 |
| Sonnet 5 | $0.00785 | $0.00785 |
| Haiku 4.5 | $0.00393 | $0.00393 |
Grade A, and why
architext 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- architext CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for AI assistants working on the Architext tool itself (this repository). For working on architecture data inside another repo that uses Architext, the Architext Architecture Documentation section at the bottom of this file is the project-consumer contract.
[!IMPORTANT] Two things in this file are managed by
architextitself — keep all hand-written contributor guidance written as prose and tables, not bulleted lists, and leave the managed sections alone:The Architext Architecture Documentation section (the
##heading near the end of this file) is upserted byarchitext sync(crates/architext-cli/src/commands/sync/instruction_files.rs); it replaces everything from that##heading to the next##heading. Edit theAPPENDIXconst in that file andviewer/AGENTS_APPENDIX.md— never the rendered block.
architext doctor/syncalso runs an instruction-rule migration (crates/architext-core/src/domain/instruction_rules.rs): any Markdown bullet or numbered list item of 16+ characters in this file gets extracted intodocs/architext/data/rules.jsonand a pointer section is appended. Tables and prose are left untouched. This guide is intentionally bullet-free sodoctorleaves it alone and does not flood the curatedrules.json. Keep it that way.
AGENTS.mdis kept byte-identical to this file.
What Architext Is
Architext is a local, project-owned architecture / release / rules / dataflow
viewer generated from strict JSON. Target projects own only JSON data (under
docs/architext/data/); the viewer, schema, and tooling are owned by the
globally installed architext package. The machine-readable model is the source
of truth, and the rendered site is a projection for humans.
Distribution is native-only (the 1.7.0 cutover removed a previous JS CLI;
there is no Node runtime and no npm channel). Architext ships as a single
self-contained Rust binary with the WASM viewer embedded, delivered via
install.sh, GitHub-release binaries, and architext update. See README.md
for the product framing and ROADMAP.md for direction.
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 · 268 lines · 3,926 tokens per session scan A cf51c661f4e1
architext AGENTS.md is an instructions file published in the GitHub repository robot-accomplice/architext (15 stars, last pushed 21d ago), licensed MIT. It adds 3,926 tokens to every session, about $0.0196 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.