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 agentmods add commands/chanmeng666/archlang/regengit 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/commands/chanmeng666/archlang/regen)<a href="https://agentmods.dev/commands/chanmeng666/archlang/regen"><img src="https://agentmods.dev/badge/commands/chanmeng666/archlang/regen.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00648 |
| Opus 5 | $0.00005 | $0.00324 |
| Sonnet 5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
regen 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regenerate generated artifacts
Run every single-source generator and inspect exactly what moved.
Steps
-
npm run gen:all— runs all eight generators (gen:grammars,gen:errors,gen:cli,gen:spec,gen:llms,gen:gbnf,gen:plan-schema,gen:intent-schema). -
Show the diff over the generated artifact set (the nine files these eight generators emit):
git diff --stat -- \ editors/archlang.tmLanguage.json \ playground/src/arch-language.js \ docs/error-codes.md \ docs/cli-reference.md \ spec.llm.md \ llms-full.txt \ grammars/archlang.gbnf \ schemas/plan.schema.json \ schemas/intent.schema.jsonDo not skim past
docs/cli-reference.md. It is generated fromsrc/manifest.ts, so any CLI change at all — a new flag, a renamed one, a reworded example — lands there and nowhere else. It is the artifact that moves most often. -
If any artifact changed WITHOUT a corresponding source change, STOP and investigate. Every generated byte must trace to an edit in a source of truth:
Generated artifact(s) Source of truth editors/archlang.tmLanguage.json,playground/src/arch-language.jssrc/grammar/tokens.ts(+ thescripts/gen-grammars.tstemplate /--syn-*values)docs/error-codes.mdsrc/error-catalog.tsdocs/cli-reference.mdsrc/manifest.ts(every command, its exact flag set, itsexamples[])spec.llm.mdsrc/grammar/tokens.ts+examples/llms-full.txtspec.llm.md+SKILL.md+src/manifest.ts+src/error-catalog.tsgrammars/archlang.gbnfsrc/grammar/tokens.tsschemas/plan.schema.jsonPLAN_JSON_SCHEMAschemas/intent.schema.jsonINTENT_JSON_SCHEMAA diff with no matching source edit means either uncommitted drift you are about to fix, or a nondeterministic generator — chase it down, do not commit the mystery.
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 · 57 lines · 9 tokens per session scan A 818274114326
regen is a command published in the GitHub repository ChanMeng666/archlang (8 stars, last pushed 3d ago), licensed MIT. It adds 9 tokens to every session and 648 once invoked, about $0.0000 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.
Other commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
tokenless-stats
Show Tokenless compression statistics.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
release
Create a new release for the Starpod workspace.
cadence-check
Run structural coherence check on a draft.