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/mamahoos/dot-filesWrote 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/mamahoos/dot-files/graphify)<a href="https://agentmods.dev/rules/mamahoos/dot-files/graphify"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/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/mamahoos/dot-files/graphify"><img src="https://agentmods.dev/badge/rules/mamahoos/dot-files/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.00262 | $0.00262 |
| Opus 5.5 | $0.00105 | $0.00105 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
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 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 graphify — 17 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
This project has a graphify knowledge graph at graphify-out/.
MANDATORY: run graphify before Read, Grep, Glob, or Bash exploration — for you and for every subagent you spawn, so include this rule in any subagent prompt that explores code. Do not skip it because the files are "already known" or because you are executing a plan; the graph surfaces cross-file and INFERRED edges that grep and Read cannot.
graphify query "<question>"— scoped subgraph for a codebase or architecture questiongraphify path "<A>" "<B>"— dependency path between two symbolsgraphify explain "<concept>"— all nodes related to a concept
Go straight to Read/Grep/Glob only when graphify has already oriented you and you need specific lines, or when graphify-out/graph.json does not exist.
Prefer graphify-out/wiki/index.md over raw files when it exists. Read graphify-out/GRAPH_REPORT.md only for broad architecture review when query/path/explain are not enough. After modifying code files, run graphify update . (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.
- 1mo ago Changed · -5 lines · -32 tokens per session 77ee99e22806
- 1mo ago First seen · 22 lines · 294 tokens per session scan A f8acb02fb5f0
graphify is a cursor rule published in the GitHub repository mamahoos/dot-files (5 stars, last pushed 2d ago), licensed MIT. It adds 262 tokens to every session, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to graphify, differing in 17 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.