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/Malnati/vaults-diagram-toolsWrote 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/malnati/vaults-diagram-tools/source-diagrams-tooling)<a href="https://agentmods.dev/rules/malnati/vaults-diagram-tools/source-diagrams-tooling"><img src="https://agentmods.dev/badge/rules/malnati/vaults-diagram-tools/source-diagrams-tooling.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.00178 |
| Opus 5 | $0.00000 | $0.00089 |
| Sonnet 5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
source-diagrams-tooling 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 7d 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
vaults-source-diagramsounode packages/source-diagrams/source-diagrams.mjspara gerar diagramas a partir de código-fonte. - Para diagramas focados, use
--filesou--files-frome validemanifest.selection. - Confirme que nós, conectores e labels do
.mmdbatem com imports/relacionamentos reais do código-fonte. - Use
--render-mode placeholdersomente para testes lógicos rápidos. - Para entrega real, preserve
.mmd,.svg,.jpg,INDEX.mde manifest quando aplicável.
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.
- 7d ago First seen · 15 lines · 0 tokens per session scan A 2c9e9476f366
source-diagrams-tooling is a cursor rule published in the GitHub repository Malnati/vaults-diagram-tools (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 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
agents-shipgate
Run Agents Shipgate as the deterministic merge gate for AI-generated agent capability changes.
uv
This project is a uv workspace with multiple members (see pyproject.toml [tool.uv.workspace]).
architectural-and-structural-rules
The project follows a layered architecture with clear separation of concerns.
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.