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/decolua/9remoteWrote 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/decolua/9remote/graphify)<a href="https://agentmods.dev/rules/decolua/9remote/graphify"><img src="https://agentmods.dev/badge/rules/decolua/9remote/graphify/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/decolua/9remote/graphify"><img src="https://agentmods.dev/badge/rules/decolua/9remote/graphify.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.00294 | $0.00294 |
| Opus 5.5 | $0.00118 | $0.00118 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
graphify 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 17d 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
This project has a graphify knowledge graph at graphify-out/.
MANDATORY: Before using Read, Grep, Glob, or Bash to explore the codebase, you MUST run graphify first:
graphify query "<question>"— scoped subgraph for any codebase or architecture questiongraphify path "<A>" "<B>"— dependency path between two symbolsgraphify explain "<concept>"— all nodes related to a concept
This applies to YOU and to every subagent you spawn. Include this rule explicitly in every subagent prompt that involves code exploration. Do not skip graphify because files are "already known" or because you are executing a plan — the graph surfaces cross-file dependencies and INFERRED edges that grep and Read cannot find.
Only use Read/Grep/Glob directly when:
- graphify has already oriented you and you need to modify or debug specific lines
graphify-out/graph.jsondoes not exist yet
- If
graphify-out/wiki/index.mdexists, navigate it instead of reading raw files - Read
graphify-out/GRAPH_REPORT.mdonly for broad architecture review when query/path/explain do not surface enough context - After modifying code files, run
graphify update .to keep the graph current (AST-only, no API cost)
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.
- 17d ago First seen · 22 lines · 294 tokens per session scan A f8acb02fb5f0
graphify is a cursor rule published in the GitHub repository decolua/9remote (190 stars, last pushed 5d ago), licensed Apache-2.0. It adds 294 tokens to every session, about $0.0012 per session on Opus 5.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-09-29.
Other cursor rules, from other repositories
999_memb_context
The following knowledge was automatically retrieved from the memB vector engine.
avos-agent-workflow
Avos memory workflow for AI coding agents. Guides codebase search and history lookup.
memory-five-layers
Sistema de memória persistente entre sessões — carregamento de contexto + salvamento explícito + watcher automático.
agent-continuity-protocol
Agent continuity protocol - lightweight new-session state check, task ledger, and stale-file prevention for Codex/Cursor/Claude collaboration.
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.