archlang-brief-to-plan

archlang-brief-to-plan is a skill for Claude Code from ChanMeng666/archlang. It costs 115 tokens per session (1,053 once invoked), scanned A, original, MIT.

A workflow that turns a written room-and-site brief into an ArchLang floor-plan file. ArchLang is a file format and command-line tool for describing and checking floor plans.

In plain words
What is it for?
Use it to create a new floor plan for a home or office from a written brief, compile it to an SVG drawing, and check the result against the stated requirements.
Why use it?
It helps translate requirements such as rooms, areas, connections, windows, and plot size into a checked plan without silently changing conflicting numbers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the archlang plugin — 5 skills shipped together

Good fit Use it to create a new floor plan for a home or office from a written brief, compile it to an SVG drawing, and check the result against the stated requirements.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chanmeng666/archlang/archlang-brief-to-plan
Install

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.

Any agent
npx skills add ChanMeng666/archlang --skill archlang-brief-to-plan
Clone the repo
git clone --depth 1 https://github.com/ChanMeng666/archlang

Made for: Claude Code.

Or install archlang, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for archlang-brief-to-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/chanmeng666/archlang/archlang-brief-to-plan/github.svg)](https://agentmods.dev/skills/chanmeng666/archlang/archlang-brief-to-plan)
Your own site
<a href="https://agentmods.dev/skills/chanmeng666/archlang/archlang-brief-to-plan"><img src="https://agentmods.dev/badge/skills/chanmeng666/archlang/archlang-brief-to-plan/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.

agentmods 80×15 button for archlang-brief-to-plan

Your own site · 80×15
<a href="https://agentmods.dev/skills/chanmeng666/archlang/archlang-brief-to-plan"><img src="https://agentmods.dev/badge/skills/chanmeng666/archlang/archlang-brief-to-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 115 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,053 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00115 $0.01053
Opus 5.5 $0.00046 $0.00421
Sonnet 5.5 $0.00023 $0.00211
Haiku 4.5 $0.00012 $0.00105

Measured today against content hash 42daa8ce6334, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

archlang-brief-to-plan 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.

plugins/archlang/skills/archlang-brief-to-plan/SKILL.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brief to plan

Turn a written brief into a checked .arch floor plan. Every step is a CLI call; never judge the plan from the SVG markup. If archlang is not on the path, write npx -y @chanmeng666/archlang in its place. Never run a bare arch: on Linux, macOS and Git Bash that name is the coreutils command.

This skill is a workflow, not a language reference. The language is whatever archlang spec prints.

Steps

  1. Read the language. Run archlang spec and read all of it before writing a line. For one command's flags and examples run archlang <cmd> --help, for example archlang finish --help.
  2. List what the brief asks for. Write down each room, each stated area, each stated connection ("opens off the hall"), each stated window, and any outer size. Keep numbers exactly as the brief states them. If two requirements cannot both hold, stop and tell the user which ones; do not quietly change a number.
  3. Write plan.arch. Give every room an id, a label and a uses. Attach doors and windows to walls and place furniture by anchor, as archlang spec shows, instead of computing coordinates. Give every room a door or an opening.
  4. Compile. archlang compile plan.arch -o plan.svg --json. If ok is false, read each diagnostics[].fix. Preview the mechanical fixes with archlang fix plan.arch --dry-run --json, then apply them with archlang fix plan.arch. Fix the rest by hand and compile again.
  5. Check the plan against your list. archlang describe plan.arch --select rooms,doors,windows,totals --json. Compare room count, labels, each area, what each door connects and which rooms have windows with the list from step 2. Edit and repeat from step 4 until they match. area_m2 is measured on wall centrelines; net_area_m2 is the floor no wall stands on.
  6. Check soundness. archlang lint plan.arch --json. Fix each warning, or keep it on purpose and say why. If a room cannot be reached or a bedroom has no window, archlang suggest plan.arch --json returns door and window statements you can paste.
  7. Finish the drawing. archlang finish plan.arch --dry-run --json shows the furniture and sheet statements it would add; archlang finish plan.arch applies them. Read unresolved: it names each room left empty and each statement left out, with the reason.
  8. Gate and show. archlang validate plan.arch --strict --json must exit 0, or you must be able to name each remaining warning as deliberate. Then archlang preview plan.arch -o plan.png to show the user.

Read the full file on GitHub · 61 lines

Changes

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.

  1. today Changed · +4 lines · +1 tokens per session 42daa8ce6334
  2. 4d ago First seen · 57 lines · 114 tokens per session scan A 28c6ad633271

Subscribe to this mod's changes

archlang-brief-to-plan is a skill published in the GitHub repository ChanMeng666/archlang (18 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 1,053 once invoked, about $0.0005 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-10-10.