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.
git clone --depth 1 https://github.com/yellow-hammer/ivolgaqlWrote 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/rules/yellow-hammer/ivolgaql/ivolgaql-parser-language)<a href="https://agentmods.dev/rules/yellow-hammer/ivolgaql/ivolgaql-parser-language"><img src="https://agentmods.dev/badge/rules/yellow-hammer/ivolgaql/ivolgaql-parser-language.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.1 | $0.00000 | $0.00279 |
| Opus 5 | $0.00000 | $0.00139 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
ivolgaql-parser-language 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 8d 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.
What it actually says
Парсер и язык запросов
- Ключевые слова — в нижнем регистре в том же наборе, что задаёт лексер; имена таблиц и столбцов не принудительно приводить к lower — сохраняй регистр из текста запроса.
- Новые команды или операторы — симметрично: лексер → разбор → при необходимости
engineи ответы вprotocol(src/parser.rs,src/engine.rs,src/protocol.rs). - Сообщения ошибок разбора и лексики — по-русски, без англоязычного жаргона в пользовательской части.
- Строковые литералы: одинарные кавычки, кавычка внутри — удвоение (
''). - После изменения грамматики обнови текст
помощь(ответ сервера) и при необходимости README. - Есть unit-тесты в
parser.rs,engine.rs,protocol.rs— прогониcargo testпосле смены поведения.
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.
- 8d ago First seen · 15 lines · 0 tokens per session scan A e15d5061d0c3
ivolgaql-parser-language is a cursor rule published in the GitHub repository yellow-hammer/ivolgaql (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 279 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-31.
Other cursor rules, from other repositories
1c-extension-patterns
A set of rules and examples for extending 1C configurations with BSL code and XML role metadata. 1C is an enterprise business-application platform, and BSL is its programming language.
testing-patterns
A set of rules and examples for testing 1C code with YaXUnit and Vanessa Automation. YaXUnit is used for unit tests of individual functions, while Vanessa Automation describes user scenarios as “given, when, then” steps.
integrations
A development rule for building 1C integrations with external systems through HTTP APIs. It recommends first making and testing the requests in Python, then translating the working version into 1C’s BSL language.
fix-galo
SYNTAX RULES.
111-java-object-oriented-design
Java Object-Oriented Design Guidelines.
131-java-refactoring-with-modern-features
Modern Java Development Guidelines (Java 8+).