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 rules/k-kolomeitsev/data-structure-protocol/dsp-public-api-changesgit clone --depth 1 https://github.com/k-kolomeitsev/data-structure-protocolWhat 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.00009 | $0.00454 |
| Opus 5 | $0.00005 | $0.00227 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
dsp-public-api-changes 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 2d 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
DSP — Public API Changes
When changing a module's public API (exported functions, classes, interfaces), update DSP shared/exports to keep the graph accurate.
Shared entries are UIDs of existing entities, not export names. To share a new export, register it first (create-function/create-object), then pass its UID to create-shared.
When Adding a New Public Export
# Find the exporting module
dsp-cli find-by-source <file-path>
# Register the exported entity, then share its UID
dsp-cli create-function "<file-path>#<ExportName>" "<what it does>" --owner <module-uid>
# → func-1a2b3c4d
dsp-cli create-shared <module-uid> func-1a2b3c4d
When Removing a Public Export
# Check who consumes it first
dsp-cli get-recipients <export-uid>
# Remove only if no active consumers, or after updating consumers
dsp-cli remove-shared <module-uid> <export-uid>
When Renaming a Public Export
The UID stays the same — only the source reference changes:
dsp-cli move-entity <export-uid> "<file-path>#<NewName>"
# Update consumers' import reason if the meaning changed
dsp-cli update-import-why <consumer-uid> <export-uid> "<updated reason>" --exporter <module-uid>
If the export changed its purpose (not just the name), retire the old entity and create a new one: remove-shared + remove-entity, then create-function + create-shared.
Checklist
- All new public functions/classes/interfaces have entities and are registered with
create-shared - Removed exports are cleaned up with
remove-shared - Consumers of changed exports are updated or notified
-
get-recipientsreturns expected results after changes
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.
- 2d ago First seen · 54 lines · 9 tokens per session scan A f3accdc7cc44
dsp-public-api-changes is a cursor rule published in the GitHub repository k-kolomeitsev/data-structure-protocol (65 stars, last pushed 23d ago), licensed Apache-2.0. It adds 9 tokens to every session and 454 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
edt-form-xml-requirements
Требования EDT к XML-формам (Form.form): extInfo, дефолты полей.
async-methods-1c
Асинхронные методы 1С: Асинх/Ждать/Обещание (8.3.18+).
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.
1c-form-reserved-names
Зарезервированные имена свойств в модулях форм 1С.
routine_assignment_ext_processor
Фоновые задания из внешней обработки через БСП.