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/real-limitless/ansible-flow-mcpWrote 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/real-limitless/ansible-flow-mcp/graphify)<a href="https://agentmods.dev/rules/real-limitless/ansible-flow-mcp/graphify"><img src="https://agentmods.dev/badge/rules/real-limitless/ansible-flow-mcp/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/real-limitless/ansible-flow-mcp/graphify"><img src="https://agentmods.dev/badge/rules/real-limitless/ansible-flow-mcp/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 | $0.00147 | $0.00147 |
| Sonnet 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 yesterday.
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 — 18 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: 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.
- yesterday First seen · 22 lines · 294 tokens per session scan A f8acb02fb5f0
graphify is a cursor rule published in the GitHub repository real-limitless/ansible-flow-mcp (3 stars, last pushed today), licensed Apache-2.0. It adds 294 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to graphify, differing in 18 lines, and is treated as a copy.
Other cursor rules, from other repositories
misakanet-failure-memory
Search MisakaNet failure-memory before debugging common errors.
debug-capture-pipeline
Debug llm-wiki-memory capture/recall — flush breadcrumbs, daily-vs-compile lag, failed-distill stash recovery, embedding cache, hook wiring. Use when memory didn't capture, doesn't recall, or a hook/cron looks broken.
memorywhale
Query and write durable debugging memory recorded by MemoryWhale. Use when a build/test/deploy is failing and might have failed before, when you need the exact error/flags/output from an earlier attempt, when the user asks "how did we fix this last time?", or once you've figured out why something failed / how a fix…
codebase-memory-index.freshness
Rules for keeping a codebase memory index up to date. A codebase memory index is a searchable record of a repository's code and relationships used by agent tools.
memory-informed-debug
Use when diagnosing bugs, errors, failing tests, or crashes — consult prior debug outcomes and capture root causes in-flight.
synapse
Rules for using Synapse MCP — prefer the graph over grep.