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 skills add ChanMeng666/archlang --skill archlang-review-plangit 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/skills/chanmeng666/archlang/archlang-review-plan)<a href="https://agentmods.dev/skills/chanmeng666/archlang/archlang-review-plan"><img src="https://agentmods.dev/badge/skills/chanmeng666/archlang/archlang-review-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.
<a href="https://agentmods.dev/skills/chanmeng666/archlang/archlang-review-plan"><img src="https://agentmods.dev/badge/skills/chanmeng666/archlang/archlang-review-plan.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.00090 | $0.01071 |
| Opus 5.5 | $0.00036 | $0.00428 |
| Sonnet 5.5 | $0.00018 | $0.00214 |
| Haiku 4.5 | $0.00009 | $0.00107 |
Grade A, and why
archlang-review-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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review a plan
Report what is true of a .arch plan and what is wrong with it, from the compiler's own facts.
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. Run archlang spec for the language,
archlang context --section errors for the diagnostic catalog, and archlang <cmd> --help for flags.
The checks are drafting heuristics. They do not establish that a plan meets a building code, and your report must not say that it does.
Steps
- Does it compile?
archlang validate plan.arch --json. Errors come first in the report; a plan with errors has no facts to review until they are fixed. - Read the facts.
archlang describe plan.arch --jsongives rooms with areas and uses, what each door and window connects, the access graph and the totals. On a large plan narrow it:archlang describe plan.arch --select rooms,access,totals --json.area_m2is measured on wall centrelines, so it counts the wall bands that stand on the room;net_area_m2subtracts them. Say which one you quote. - Run the default lint.
archlang lint plan.arch --json. Each warning has a code, a place in the source and afixin prose.archlang explain <CODE> --jsonexplains a code you do not know. - Run the accessibility profile when the user asks about access, or when the brief mentions
a wheelchair, step-free access or ageing in place:
archlang lint plan.arch --profile accessibility-advisory --json. - Check against the brief, if there is one. Write the brief's checkable requirements as an
intent file: room count only if the brief lists the rooms, an area band only where the brief
gives a number. The format is the JSON Schema at https://archlang.uk/intent.schema.json,
explained at https://archlang.uk/intent; a malformed file is refused with exit
3and the path of the bad field. Then runarchlang validate plan.arch --intent intent.json --feedback --json. A failed gating assertion exits2and comes with a correction prompt for each violation.archlang score plan.arch --brief intent.json --jsongives the same comparison as a number that never fails. - Ask for candidate fixes. For an unreachable room, a building with no entrance, a bathroom
reached only through a bedroom, or a bedroom with no window,
archlang suggest plan.arch --jsonreturns door and window statements with a reason for each. Put them in the report as options. Do not apply them. - Look at it, if that helps.
archlang preview plan.arch --asciiprints a text plan;archlang preview plan.arch -o plan.pngrenders an image.archlang compile plan.arch --overlay circulation -o walk.svgdraws the walking routes and their narrow points.
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.
- today Changed · +3 lines · +1 tokens per session 9505072d6705
- 4d ago First seen · 65 lines · 89 tokens per session scan A 871dd7617f46
archlang-review-plan is a skill published in the GitHub repository ChanMeng666/archlang (18 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,071 once invoked, about $0.0004 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.
Other skills, from other repositories
ouroboros-run
Execute a Seed specification through the workflow engine.
evolve
Start or monitor an evolutionary development loop.
ouroboros-status
Check session status and measure goal drift.
ooo
Start Ouroboros onboarding. Use when the user sends bare ooo, asks to start Ouroboros, or is using Ouroboros for the first time.
animate
Build a web animation: whether it should animate at all, the purpose, the tool, the properties, the easing curve, the duration, interruption and exit. Writes the CSS or Motion code for dropdowns, modals, toasts, tooltips, accordions, press feedback, stagger and scroll reveals. Use to animate something or make a…
marketing
Use when the words span a marketing surface — value proposition, section copy, microcopy, launch and email sequences, channel adaptation, SEO-aware structure — grounded in the brand study, which it stops and builds if missing. NOT one conversion page (that is landing-copy), NOT tone rules (that is brand-voice), NOT…