A development command for adding a new ArchLang element through the project’s registry. ArchLang is a language whose elements are parsed, resolved, and rendered by the compiler.

Use it to add an element module, register it, write tests, and regenerate generated language files when new syntax is introduced.

It gives the new element one defined path through the compiler and keeps error reporting, formatting, and tests consistent.

new-element — Command for Claude Code by ChanMeng666: A development command for adding a new ArchLang element…

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.

agentmods

npx agentmods add commands/chanmeng666/archlang/new-element

Clone the repo

git clone --depth 1 https://github.com/ChanMeng666/archlang

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/chanmeng666/archlang/new-element.svg)](https://agentmods.dev/commands/chanmeng666/archlang/new-element)

Your own site

<a href="https://agentmods.dev/commands/chanmeng666/archlang/new-element"><img src="https://agentmods.dev/badge/commands/chanmeng666/archlang/new-element.svg" alt="Measured on agentmods" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 450 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00450
Opus 5	$0.00005	$0.00225
Sonnet 5	$0.00002	$0.00090
Haiku 4.5	$0.00001	$0.00045

Measured 3d ago against content hash 5efddf6a20a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

new-element 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 3d 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.

.claude/commands/new-element.md · 38 lines

What it actually says

Add a new element

Elements are added through the registry, never a switch. Dispatch (parse / resolve / render) goes through src/elements/defs.ts.

Steps

Create src/elements/<name>.ts exporting an ElementDef (follow an existing module in src/elements/ as the template — e.g. a simple leaf element).
Register it in src/elements/defs.ts. Add it to the registry so parse, resolve, and render all dispatch to it automatically. Do not add a switch branch anywhere.
Keep the compiler pure. No I/O, no Date.now(), no Math.random() in the element module. Coordinates are millimetres; origin top-left, +x right, +y down. Route number formatting through fmt() so output stays byte-stable. Errors for bad user source are returned as a Diagnostic with a byte span and a catalogued E_*/W_* code in src/error-catalog.ts (a test enforces every raised code has an entry), never thrown.
Add unit tests in test/ covering parse, resolve, and render for the new element.
npm run gen:all — if the element introduces new tokens/keywords, the generated spec, grammars, GBNF, and schemas must pick them up. (Regeneration is source-driven; never hand-edit the generated artifacts — see /regen.)
Run /verify-loop — npm run check + npm run check:drift must be green.

Remember

examples/studio.arch is the flagship and must stay lint-clean and import-free (test/world.test.ts asserts it compiles from a single file with no World). If your element changes anything the flagship exercises, keep it clean — use inline furniture <fixture> there, not imports.

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.

3d ago First seen · 38 lines · 10 tokens per session scan A 5efddf6a20a1

Subscribe to this mod's changes

new-element is a command published in the GitHub repository ChanMeng666/archlang (8 stars, last pushed 3d ago), licensed MIT. It adds 10 tokens to every session and 450 once invoked, about $0.0001 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.

Languages agentic-ai ai-agents architecture cad cli compiler

new-element

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Add a new element

Steps

Remember

What this file has done since we first saw it

Other commands, from other repositories

oss-docs

go

dev

code-simplify

plan

test