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/spec-fn-naming)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/spec-fn-naming"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/spec-fn-naming/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/spec-fn-naming"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/spec-fn-naming.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.00431 | $0.00431 |
| Opus 5 | $0.00216 | $0.00216 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
spec-fn-naming 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 9d 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
Spec Function Naming
No _post suffix
Name spec functions after the operation they specify, not as postconditions:
// Bad: _post suffix
pub open spec fn spec_ninject_post<T>(...) -> bool { ... }
// Good: named after the operation
pub open spec fn spec_ninject<T>(...) -> bool { ... }
The spec_ prefix already signals this is a specification. Adding _post is redundant and inconsistent with the rest of the codebase (spec_inject, spec_iterate, spec_monoid, etc.).
Pattern
| Operation | Spec function |
|---|---|
| inject | spec_inject |
| ninject | spec_ninject |
| iterate | spec_iterate |
| monoid | spec_monoid |
| filter_len | spec_filter_len |
Well-formedness spec naming: spec_<module>_wf
Name well-formedness specs spec_<module>_wf where <module> is the module name in
lowercase with no internal underscores. Do not use bare spec_wf.
// Bad: bare spec_wf
spec fn spec_wf(&self) -> bool;
// Good: module name smushed lowercase
spec fn spec_orderedtablestper_wf(&self) -> bool;
spec fn spec_augorderedtablemteph_wf(&self) -> bool;
| Module | spec_wf name |
|---|---|
| AVLTreeSeq | spec_avltreeseq_wf |
| AVLTreeSeqStEph | spec_avltreeseqsteph_wf |
| AVLTreeSeqStPer | spec_avltreeseqstper_wf |
| OrderedTableStPer | spec_orderedtablestper_wf |
| AugOrderedTableMtEph | spec_augorderedtablemteph_wf |
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.
- 9d ago First seen · 54 lines · 431 tokens per session scan A c793f1c046d0
spec-fn-naming is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 1mo ago), licensed MIT. It adds 431 tokens to every session, about $0.0022 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 cursor rules, from other repositories
core
Core STT/TTS abstraction layer documentation.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-development-standards
Rust development standards: idioms, style, anti-patterns (Rust 2021 edition, 2024 where applicable).
ivolgaql-project
General development rules for ИволгаQL, an early-stage Rust project with a command-line and TCP server interface. They define the project structure, Russian user experience, coding conventions, testing, builds, and commit-message format.
rust-native-architecture
Enforces native-first architecture and crate boundary rules for the nca workspace.