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 agents/nickzaitsev/ru-normalizr/stage-orderinggit clone --depth 1 https://github.com/NickZaitsev/ru-normalizrWrote 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/agents/nickzaitsev/ru-normalizr/stage-ordering)<a href="https://agentmods.dev/agents/nickzaitsev/ru-normalizr/stage-ordering"><img src="https://agentmods.dev/badge/agents/nickzaitsev/ru-normalizr/stage-ordering.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.00000 | $0.00648 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
stage-ordering 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage ordering: the specific pattern runs first
Every stage is a set of greedy regexes over the whole text. There is no arbitration: whichever stage reaches a span of characters first claims it, and the stage that would have matched a longer, more specific span gets whatever debris is left. Debris is worse than no match at all, because it is usually still numeric and the numerals stage will happily read it as something.
Three bugs of exactly this shape have been fixed so far:
| Winner took | Loser got | Symptom |
|---|---|---|
decimals took 3.12 |
.1 |
Python 3.12.1 → три целых двенадцать сотых. Одного |
years took 2021 года |
15.03. |
15.03.2021 года → пятнадцать целых три сотых. Две тысячи… |
decimals took 5.2 |
10- |
10-5.2 → десять пять целых две десятых (separator gone) |
In each case the orphan's trailing dot became a sentence boundary in
detokenize, and because NUMERAL_CONTEXT_BARRIERS does not include .,
get_numeral_case scanned straight across it and inflected the stranded number
to agree with words from the previous "sentence".
The rule
A full date is a special case of a year; a version is a special case of a
decimal; a range is a special case of two numbers. The special case must run
first. normalize_text therefore runs dates_time before years, and
normalize_versions before normalize_decimals.
The same rule applies to authority, not just to span length: an explicit
instruction outranks a guess. dictionary therefore runs before
latinization — while it ran second it could not match any Latin token in TTS
mode, because latinization had already rewritten the token into Cyrillic, so
user rules were silently ignored in the pipeline's main mode.
Reordering is usually right, but never free
Putting the specific stage first is the correct fix, not a workaround. But a
stage that has spent its whole life running second can carry latent defects
that only the first position exposes. Reordering dates_time before years
unmasked two of them at once: the shared year fragment consumed the whitespace
before an optional era word (…двадцатого годаг.), and the dotted date pattern
had no era tail at all.
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.
- 5d ago First seen · 49 lines · 0 tokens per session scan A ea8a98a4278d
stage-ordering is an agent published in the GitHub repository NickZaitsev/ru-normalizr (22 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 648 tokens. 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-30.
Other agents, from other repositories
RULES
Agent "RULES" from phel-lang/phel-lang, covering phel rules + cli, rules, new features (v0.30 – main), gotchas and cli.
fixture-reviewer
Audits .test integration fixtures under tests/php/Integration/Fixtures for drift against the current compiler output. Use after lexer, parser, analyzer, or emitter changes.
module-docs-sync
Audits and updates CLAUDE.md files in src/php/ modules to match the actual code. Use after large refactors, new modules, or periodic maintenance.
tdd-coach
Guides test-driven development with red-green-refactor discipline. Use when implementing features or fixes with TDD.
quick-syntax
One-screen cheatsheet. For exhaustive rules see RULES.md; for typing details see tasks/typed-defn.md.
owner-judge
Reviews proposed changes to VoiceStudio against the owner's documented standards. Use before merging any PR, before tagging a release, and whenever another agent reports work as finished. Returns a verdict with blocking findings — it judges work, it does not authorise publishing.