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/alkoleft/platform-context-exporterWrote 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/alkoleft/platform-context-exporter/rule-calling-help)<a href="https://agentmods.dev/rules/alkoleft/platform-context-exporter/rule-calling-help"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/rule-calling-help/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/alkoleft/platform-context-exporter/rule-calling-help"><img src="https://agentmods.dev/badge/rules/alkoleft/platform-context-exporter/rule-calling-help.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.00133 |
| Opus 5.5 | $0.00000 | $0.00053 |
| Sonnet 5.5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
rule-calling-help 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 1mo 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.
This is a copy
100% identical to rule-calling-help — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
VAN QA: HOW TO CALL RULES
TL;DR: This file provides examples and reminders on how to properly call VAN QA rules using the fetch_rules tool.
🚨 RULE CALLING SYNTAX
Always use the fetch_rules tool with the correct syntax:
<function_calls>
<invoke name="fetch_rules">
<parameter name="rule_names">["isolation_rules/visual-maps/rule-name"]
</invoke>
</function_calls>
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.
- 1mo ago First seen · 19 lines · 0 tokens per session scan A a553fd04fac6
rule-calling-help is a cursor rule published in the GitHub repository alkoleft/platform-context-exporter (49 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 133 tokens. A static security scan graded it A with 0 findings. It is 100% identical to rule-calling-help, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
1c-coding-standards
Coding standards for BSL, the programming language used by the 1C business software platform. They cover naming, method documentation, database queries, collections, client-server code, and performance practices.
code-review-checklist
A code-review checklist for 1C source files, including BSL and OS files. It groups findings by severity and checks issues such as security, performance, errors, access control, duplication, and maintainability.
bsl-ssl
A set of rules for developing 1C applications built on БСП, the Russian-language Standard Subsystems Library. It tells developers when to reuse library functionality, how to mark changes, and how to handle outdated objects.
1c-report-direct-query
A 1C reporting rule that runs the report query directly instead of using the standard data-composition engine (СКД). It then displays or exports the returned table manually.
1c-transactions-and-locks
Guidance for using transactions and controlled locks in 1C, where a transaction groups database changes so they can be accepted or cancelled together. It also explains the order in which locks should be taken when several operations share data.
query-optimization-tips
A set of tips for making 1C database queries run faster. 1C is a business software platform, and these rules cover query writing and review.