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/briangmilnes/APAS-VERUSWrote 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/briangmilnes/apas-verus/xlit-macros)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/xlit-macros"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/xlit-macros/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/rules/briangmilnes/apas-verus/xlit-macros"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/xlit-macros.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.00000 | $0.00356 |
| Opus 5 | $0.00000 | $0.00178 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
xlit-macros 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
Use XLit! Macros for Constructing Values
In APAS-VERUS, all data types have a literal macro XLit! which should be used to construct values of that type in runtime and proof time testing.
Available Macros
| # | Data Type | Macro | Example |
|---|---|---|---|
| 1 | SetStEph | SetLit! |
SetLit![1, 2, 3] |
| 2 | RelationStEph | RelationLit! |
RelationLit![(1, 'a'), (2, 'b')] |
| 3 | MappingStEph | MappingLit! |
MappingLit![(1, 'a'), (2, 'b')] |
| 4 | Pair | PairLit! |
PairLit!(1, 'a') |
Imports
When using macros, import them from apas_verus:
use apas_verus::{SetLit, RelationLit, MappingLit, PairLit};
For RelationLit! and MappingLit!, also import SetStEphTrait:
use apas_verus::Chap05::SetStEph::SetStEph::*;
Runtime Safety
MappingLit! includes a duplicate-key check that panics at runtime if the same key appears twice. This check is skipped in Verus proof mode (the from_vec precondition handles verification).
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 · 37 lines · 0 tokens per session scan A bfcec21e82ec
xlit-macros is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.