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 skills add widnyana/eyay-toolkits --skill design-graphgit 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/design-graph)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/design-graph"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/design-graph/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/skills/widnyana/eyay-toolkits/design-graph"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/design-graph.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.00073 | $0.03050 |
| Opus 5.5 | $0.00029 | $0.01220 |
| Sonnet 5.5 | $0.00015 | $0.00610 |
| Haiku 4.5 | $0.00007 | $0.00305 |
Grade A, and why
design-graph 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.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source: Design Graph by r17x, from https://gist.github.com/r17x/90eb2f7be93932b5693753aedb09c01a (
OPT_DESIGN_GRAPH.md). Method text bundled as-is. The output skeleton at the end is added by this package.
Design Graph
The same method, turned on the interface. A screen is not a picture — it is a node with three channels, and the layout you draw is the graph the user walks.
Design Thinking answers what flows through the program. Design Graph answers what the person in front of it can be looking at. Same three-channel discipline: one channel for the content, one for every way the content can be absent, one for what the surface needs before it may exist.
Job → Flow → Surface<C, V, N>
│ │ │ │ │
│ │ │ │ └─ what the surface needs to exist (§5)
│ │ │ └──── every way the content is absent (§4)
│ │ └─────── what the person reads and does (§2)
│ │
│ └─ nodes = surfaces, edges = the moves between them
│
└─ the job: what the person came here to get done
§1 Surfaces the nouns: screens, panes, rows, fields, controls
§2 C happy path as flow graph
§3 Cardinality one record (Detail) or many (List / live)
§4 V void states: empty, loading, partial, error, denied
§5 N needs: data, permission, prior step, viewport
§6 Boundary validate at the field, not at submit
§7 Behavior motion and feedback wrap a surface, never reshape it
§8 Scope attention is acquired and must be released
§9 Proof swap N, same flow shape
§10 Craft markup = C, state styles = V
Read the job. Draw the moves as a flow graph. Build an interface that IS the graph. If a surface can render a state the graph cannot name, the interface is lying.
1. Name the surfaces
What are the things a person can look at? Before opening a layout tool, define the interface language.
- Surfaces -- the addressable places. A rail, a list, a detail pane, a drawer. Each one has a name and an owner.
- Units -- the repeated shape inside a surface. A row, a field, a metric. Named once, reused everywhere.
- States -- what a unit can be. Rest, hover, selected, disabled, stale. Enumerated, not improvised at build time.
- Moves -- what the person can do to get somewhere else. Open, select, dismiss, commit, undo.
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.
- 2d ago Changed · +121 lines · +9 tokens per session 59aede5b03f5
- 17d ago Changed · +1 lines 144147aed16d
- 1mo ago Changed · +3 lines fd841a71739d
- 1mo ago First seen · 99 lines · 64 tokens per session scan A cf3e555ec31a
design-graph is a skill published in the GitHub repository widnyana/eyay-toolkits (8 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 3,050 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.
Other skills, from other repositories
data-engineering
Builds and operates data pipelines — ingestion, transformation, orchestration, quality testing, and reliability of data delivery. Use this to design or debug a pipeline, decide batch versus streaming, add data quality checks, handle late or duplicate data, or work out why a dashboard's numbers changed without anyone…
api-design
Designs interfaces that survive their consumers — resource modeling, errors, versioning, pagination, and compatibility. Use this to design a new API, review one before it ships, decide how to version or deprecate, fix an interface consumers keep misusing, or work out whether a change is breaking.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
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.