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/version-numbersgit 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/version-numbers)<a href="https://agentmods.dev/agents/nickzaitsev/ru-normalizr/version-numbers"><img src="https://agentmods.dev/badge/agents/nickzaitsev/ru-normalizr/version-numbers.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.00566 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
version-numbers 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 4d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dotted numbers: version vs. fraction
normalize_versions (numerals/versions.py) runs immediately before
normalize_decimals in PipelineNormalizer.run_numerals. It has to: the
decimals stage matches \d+[.,]\d+ unconditionally, so whatever it sees first
it claims. Any new rule about a dot between digits belongs before the
decimals stage, not inside it.
What counts as a version
Two structural signals, no list of product names:
- Three or more components (
3.12.1,192.168.1.1). A fraction cannot have two dots, so this is unambiguous. - Two components glued by a hyphen to a name (
GLM-5.2,Ту-154.2).
Signal 2 needs a guard: a named value followed by a recognized unit is a
measurement, not a version (X-1.5 кг), so _is_followed_by_unit bails out via
resolve_unit_info. Signal 2 still catches genuine measurements written without
a unit — Mach-2.5, pH-7.4 read as "два точка пять" — an accepted trade-off,
since nothing structural separates them from a model number.
Why the old behaviour was broken
DECIMAL_PATTERN took 3.12 out of Python 3.12.1 and left .1 as literal
text. detokenize then treated that orphaned dot as a sentence boundary, and
because NUMERAL_CONTEXT_BARRIERS does not include ., get_numeral_case
scanned across it, found the fraction's own сотых (ADJF plur gent) and
inflected the stranded 1 to match — producing … двенадцать сотых. Одного.
The pymorphy trap behind model numbers
Ту-154.2 used to render сто пятьдесят четырёх целых. That is not a genitive
rule: pymorphy parses Ту as the pronoun тот (ADJF femn sing accs), the
adjective-agreement scan in _helpers.get_numeral_case picks up that case, and
the accusative of четыре is syncretic with the genitive. Reading the model
number as a version sidesteps it, because version components are always
rendered in the nominative. Expect the same trap in any new rule that lets a
number inherit case from a preceding capitalized Latin or abbreviated token.
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.
- 4d ago First seen · 40 lines · 0 tokens per session scan A f6b8f8a2ef87
version-numbers 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 566 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
ai-polish-text-expert
Jestem agentem orkiestrującym zintegrowany system pracy z treściami tekstowymi w języku polskim. Zarządzam trzema wyspecjalizowanymi skills i kieruję każde żądanie do właściwego skill'a — automatycznie lub na podstawie komendy użytkownika.
compliance-checker
Agent ensuring compliance with Polish language standards and legal regulations (RODO/GDPR).
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
RULES
Agent "RULES" from phel-lang/phel-lang, covering phel rules + cli, rules, new features (v0.30 – main), gotchas and cli.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
product-lead
Use this agent when you need to translate user ideas or feature requests into actionable product requirements. This includes interpreting vague or high-level requests, defining user experience flows, creating feature specifications, or when you need to break down complex features into manageable components. The agent…