graph-protocol

graph-protocol is a skill for Claude Code from widnyana/eyay-toolkits. It costs 68 tokens per session (3,431 once invoked), scanned A, original, MIT.

A notation standard for annotated design graphs, where nodes represent functions and edges represent data flow. It defines fixed sections and symbols for failures, boundaries, repetition, scope, and test layers across different technology stacks.

In plain words
What is it for?
Use it to format Design Graphs and validate output from the package's planning, mapping, review, and active design modes.
Why use it?
It gives teams a consistent format for writing, reviewing, and checking system designs, so graphs can be compared and mechanically checked.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents; mentions Claude Code.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is "Meta Research Prompt Generator" ([meta-research.md](../../references/meta-research.md)) and.

Good fit Use it to format Design Graphs and validate output from the package's planning, mapping, review, and active design modes.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/widnyana/eyay-toolkits
agentmods
npx agentmods add skills/widnyana/eyay-toolkits/graph-protocol

Made for: Claude Code.

Wrote 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.

agentmods badge for graph-protocol

README.md
[![agentmods](https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/graph-protocol/github.svg)](https://agentmods.dev/skills/widnyana/eyay-toolkits/graph-protocol)
Your own site
<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/graph-protocol"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/graph-protocol/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.

agentmods 80×15 button for graph-protocol

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,431 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.03431
Opus 5.5 $0.00027 $0.01372
Sonnet 5.5 $0.00014 $0.00686
Haiku 4.5 $0.00007 $0.00343

Measured 2d ago against content hash 448d73379a00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2d 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.

pi-packages/design-thinking/skills/graph-protocol/SKILL.md · 314 lines

How it starts

The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Source: Graph Protocol by r17x, from https://gist.github.com/r17x/90eb2f7be93932b5693753aedb09c01a (OPT_GRAPH_PROTOCOL.md). Method text bundled as-is. The block formats at the end (execution graph, AGENT SUBGRAPH, IMPLEMENTED GRAPH, retry and evolution) are taken from r17x's "Meta Research Prompt Generator" (meta-research.md) and made generic for any delegated task.

Graph Protocol

The same method, turned on the orchestration. A task is not a checklist — it is a graph with nodes, edges, and channels, and the delegation you write is the subgraph the worker walks.

Design Thinking answers what flows through the program. Graph Protocol answers what flows through the orchestration. Same three-channel discipline: one channel for the work, one channel for where delegation breaks, one channel for what each agent needs.

X → Graph → Delegation<A, E, R>
│              │       │  │  │
│              │       │  │  └─ what each agent needs            (§5)
│              │       │  └──── where the delegation breaks      (§4)
│              │       └─────── what flows through agents        (§2)
│              │
│              └─ nodes = tasks, edges = data dependencies
│
└─ the problem: what you're trying to build

§1  Task Nodes    the nouns: files, modules, domains, workers
§2  A             happy path as execution graph
§3  Cardinality   one worker (SMALL) or many (MEDIUM/LARGE)
§4  E             break points: wrong context, missing input, misinterpretation
§5  R             requirements: subgraph, design method, verification, WHY
§6  Boundary      subgraph in, implemented graph out — structured at edges
§7  Behavior      observe wraps delegation without changing the graph
§8  Scope         worker attention is acquired and must be released
§9  Proof         compare delegated subgraph vs implemented graph
§10 Structure     prompt = subgraph, return = implemented graph

Read the problem. Draw the task flow as an execution graph. Delegate work that IS the subgraph. If the implemented graph does not match the delegated subgraph, the delegation is wrong.

Read the full file on GitHub · 314 lines

Changes

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.

  1. 2d ago Changed · +74 lines · -33 tokens per session 448d73379a00
  2. 17d ago Changed · +1 lines 4d121f98577d
  3. 1mo ago First seen · 239 lines · 101 tokens per session scan A 26d4297cdf6e

Subscribe to this mod's changes

graph-protocol is a skill published in the GitHub repository widnyana/eyay-toolkits (8 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 3,431 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

sxo

Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals…

nowork-studio/notfair-plugin · 211 tokens

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…

nowork-studio/notfair-plugin · 91 tokens

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

interface-craft

Raises the visual and interaction quality of an interface — layout, hierarchy, type, spacing, density, and the details that separate a considered product from a generic one. Use this when a screen works but looks unfinished or default, when a layout feels crowded or arbitrary, when a page has no clear focal point, or…

cbrock84/headcount · 79 tokens

paid-advertising

Plans, runs, and optimizes paid acquisition across search, social, and display — account structure, targeting, creative, bidding, budget, and the analysis that says whether to scale or stop. Use this to set up or restructure campaigns, write and iterate ad creative, diagnose rising costs or falling performance, decide…

cbrock84/headcount · 78 tokens

vendor-management

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…

cbrock84/headcount · 69 tokens