archlang: Command for Claude Code

.claude/commands/new-element.md

new-element is a command for Claude Code from ChanMeng666/archlang. It costs 10 tokens per session (659 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to add an element module, register it, write tests, and regenerate generated language files when new syntax is introduced.
Why use it?
It gives the new element one defined path through the compiler and keeps error reporting, formatting, and tests consistent.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is ChanMeng666/archlang's own configuration. It tells Claude Code how to work on archlang itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything archlang configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/ChanMeng666/archlang/main/.claude/commands/new-element.md
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.

agentmods badge for new-element

README.md
[![agentmods](https://agentmods.dev/badge/commands/chanmeng666/archlang/new-element/github.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/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 new-element

Your own site · 80×15
<a href="https://agentmods.dev/commands/chanmeng666/archlang/new-element"><img src="https://agentmods.dev/badge/commands/chanmeng666/archlang/new-element.svg" alt="Reviewed on agentmods" width="80" 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 659 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.00010 $0.00659
Opus 5.5 $0.00004 $0.00264
Sonnet 5.5 $0.00002 $0.00132
Haiku 4.5 $0.00001 $0.00066

Measured 21d ago against content hash 5b5ad044339d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 21d 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 · 48 lines

How it starts

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

Add a new element

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

Steps

  1. Create src/elements/<name>.ts exporting an ElementDef (follow an existing module in src/elements/ as the template — e.g. a simple leaf element). Give it a transform(el, t) so a placed component can carry it (test/transform-seam.test.ts requires one on every built-in); flip any handed fact when t.reflected.

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

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

  4. Declare drawCost and the range inputs. drawCost(resolved) is an upper bound on the primitives render() emits (src/draw-budget.ts; without it the kind is estimated at DEFAULT_DRAW_COST, wrong for anything that grows with its size); test/drawing-budget.test.ts checks estimate >= drawn. bounds() must list every point drawn and measures() every other coordinate or length (an opening's width, a thickness, a radius, an offset), because the resolver holds both to MODEL_RANGE_MM (E_OUT_OF_RANGE). Any loop the element runs is charged to the step budget (src/expr.ts) or capped by a constant, before it allocates.

  5. Add unit tests in test/ covering parse, resolve, and render for the new element.

  6. 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.)

Read the full file on GitHub · 48 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. 21d ago Changed · +8 lines 5b5ad044339d
  2. 26d ago Changed · +2 lines 04a35394233d
  3. 1mo 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 (24 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 659 once invoked, about $0.0000 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.