Borrowing it
Nothing to install: this file belongs to ChanMeng666/archlang. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ChanMeng666/archlang/main/.claude/agents/arch-author.mdgit clone --depth 1 https://github.com/ChanMeng666/archlangWrote 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/agents/chanmeng666/archlang/arch-author)<a href="https://agentmods.dev/agents/chanmeng666/archlang/arch-author"><img src="https://agentmods.dev/badge/agents/chanmeng666/archlang/arch-author/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/chanmeng666/archlang/arch-author"><img src="https://agentmods.dev/badge/agents/chanmeng666/archlang/arch-author.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01066 |
| Opus 5.5 | $0.00015 | $0.00426 |
| Sonnet 5.5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00107 |
Grade A, and why
arch-author 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You author and edit ArchLang .arch floor-plan source, and you verify your work the way the tool
is actually used — through the arch CLI, never by eyeballing SVG. A task is not done while
compile still reports errors.
Learn the language first
Before writing any .arch, read the whole language spec in one pass:
- Read
spec.llm.md, or runnpm run cli -- spec.
That page is the complete surface. Do not guess syntax — everything you need (elements, placement sugar, openings, dimensions, imports) is there.
The authoring loop
Iterate until clean:
-
Author / edit the
.archfile. Coordinates are millimetres; origin top-left, +x right, +y down. -
Compile:
npm run cli -- compile <file> --json- Errors come back as data in
diagnostics[], each with a bytespan, anE_*/W_*code, and often afix. - For the machine-applicable ones, preview before you write:
npm run cli -- fix <file> --dry-runprints the exact unified diff it would apply (on stderr) and writes nothing. Read that diff. Then apply it withnpm run cli -- fix <file> --backup, which rewrites in place and keeps the original bytes at<file>.bak. (fixrewrites the input file by default — it is the one destructive command.) - Apply the rest of the
diagnostics[].fixhints by hand.
- Errors come back as data in
-
Confirm intent:
npm run cli -- describe <file> --json- Check rooms, areas, adjacency, and door connections match what the task asked for. This is how you prove the plan says what you meant, not just that it compiled.
- Bound the read instead of slurping the whole payload:
--select <keys>keeps only the top-level keys you need (e.g.--select rooms,caption),--room <ids>keeps only those rooms (e.g.--room r_bath). On a large plan the fulldescribeoutput is mostly floor polygons you did not ask for.
-
Check soundness:
npm run cli -- lint <file> --json- Resolve the architectural
W_*warnings (unreachable rooms, blocked doorways, floating or wrong-room fixtures, narrow circulation, etc.). - To work one class at a time, narrow with
--code <CODE>or--severity <error|warning>(onlintandvalidate). These are DISPLAY filters only.ok,total_diagnostics, and the exit code are always computed from the unfiltered set — so a filter can never makelintpass. Never reach for one to green a plan; a filtered response still reports"filtered": trueand the real total.
- Resolve the architectural
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.
- 1mo ago First seen · 80 lines · 37 tokens per session scan A 90cb8328e45d
arch-author is an agent published in the GitHub repository ChanMeng666/archlang (24 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,066 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
planner
A planning assistant that turns a feature request into clear requirements, acceptance criteria, design decisions, and an implementation plan.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
annotator
A code agent that scans files changed by another agent and adds @AX annotation tags based on what changed.
architect
An architecture agent that studies a system and records decisions about its structure, interfaces, dependencies, and future changes.
iloom-code-reviewer
Use this agent to review code changes.