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 dkstm95/hope --skill diagramgit clone --depth 1 https://github.com/dkstm95/hopeWrote 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/dkstm95/hope/diagram)<a href="https://agentmods.dev/skills/dkstm95/hope/diagram"><img src="https://agentmods.dev/badge/skills/dkstm95/hope/diagram.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.00036 | $0.00327 |
| Opus 5 | $0.00018 | $0.00163 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00033 |
Grade A, and why
diagram 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.
What it actually says
Hope Diagram
Make the relationship or quantitative claim easier to understand. When working inside another task, preserve its scope, facts, evidence, artifact schema, visual system, and completion conditions. Improve the existing result; create another file only when the task needs one.
Read references/diagram-standard.md for visual selection, composition,
accessibility, and rendered verification. Also read references/chart-standard.md
when position, length, area, width, angle, or another visual property encodes a
quantity.
Use the smallest suitable format the host can render and the person can inspect. Respect a requested format or an artifact's allowed visual kinds. Resolve routine presentation choices from context and continue; ask only when the choice would materially change the requested result.
Inside a Hope HTML artifact, inherit its Technical Record theme, typography,
and responsive shell. A standalone HTML visual uses the same dual-mode
language; read ../../assets/artifact-theme.mjs and embed its current roles.
Inspect the result at its intended size using the standard. Fix material defects and recheck affected relationships. Before returning a created or edited visual, inspect the whole result again at its intended size. Finish only when that fresh inspection reveals no new material issue. Return the finished artifact or review findings with material assumptions, omissions, and verification gaps. A review request alone does not authorize editing its target.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -37 lines · -18 tokens per session 27c3f670ae0f
- 3d ago Changed · +6 lines 1ae77af0141c
- 8d ago First seen · 65 lines · 54 tokens per session scan A db97f0b69733
diagram is a skill published in the GitHub repository dkstm95/hope (8 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 327 once invoked, about $0.0002 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
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md. Use when user says 'generate design.md', 'extract design system', 'design tokens to markdown', 'create design doc from Figma', 'Figma design system to design.md', or wants to document their design system from token files and…
bmad-ux
Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX".
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…