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 skills/widnyana/eyay-toolkits/graph-protocolnpx skills add widnyana/eyay-toolkits --skill graph-protocolgit clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/skills/widnyana/eyay-toolkits/graph-protocol)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/graph-protocol"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/graph-protocol.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.00101 | $0.02377 |
| Opus 5 | $0.00051 | $0.01189 |
| Sonnet 5 | $0.00020 | $0.00475 |
| Haiku 4.5 | $0.00010 | $0.00238 |
Grade A, and why
graph-protocol 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Graph Protocol
The notation spec for Design Graphs. A Design Graph is the annotated call graph of a concrete problem: nodes are functions, edges are data flow, and every node carries annotations for data (A), cardinality, failure (E), and requirements (R).
The Protocol is stack-agnostic. A graph written for Go, Rust, Python, TypeScript, SQL, or a spreadsheet renders identically. Only the vocabulary inside the annotations changes (e.g. what "retry" means in your language).
Every tool in this package (/cg, /cg-plan, /cg-review, /cg-map, and the
/dt active mode) MUST emit output in the format below.
Canonical output skeleton
Sections appear in this fixed order. Omit a section only when it is genuinely
empty for the problem at hand (say so: SCOPE: none), never to skip thinking.
PROBLEM: <one-line statement of what you're building or examining>
X → DesignGraph<A, E, R>
│ │ │ │ │
│ │ │ │ └─ R: what each node needs (§5)
│ │ │ └──── E: where the graph breaks (§4)
│ │ └─────── A: what flows through nodes (§2)
│ │
│ └─ nodes = functions, edges = data flow
│
└─ the problem
SHAPES: <the nouns: records, IDs, variants, errors>
GRAPH:
<ascii call graph, annotated inline>
CARDINALITY: <node (1|N|T) list>
BOUNDARIES: <every edge crossing untrusted → trusted>
BEHAVIOR: <cross-cutting layers that wrap nodes>
SCOPE: <resources: acquire@… → release@…>
TEST LAYERS: <the R that tests provide — same GRAPH, zero code change>
VERDICT: <code matches graph? what is missing/tangled?>
The header tree
The header names the problem and anchors the three channels. X is your problem;
everything after it is the graph you build.
X → DesignGraph<A, E, R>
│ │ │ │ │
│ │ │ │ └─ R: what each node needs (§5)
│ │ │ └──── E: where the graph breaks (§4)
│ │ └─────── A: what flows through nodes (§2)
│ │
│ └─ nodes = functions, edges = data flow
│
└─ the problem: what you're trying to build
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.
- 5d ago First seen · 239 lines · 101 tokens per session scan A 26d4297cdf6e
graph-protocol is a skill published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 2,377 once invoked, about $0.0005 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-31.
Other skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.