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 wahidyankf/ose-public --skill docs-creating-accessible-diagramsgit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/docs-creating-accessible-diagrams)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-creating-accessible-diagrams"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-creating-accessible-diagrams/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/wahidyankf/ose-public/docs-creating-accessible-diagrams"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-creating-accessible-diagrams.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.00041 | $0.00767 |
| Opus 5.5 | $0.00016 | $0.00307 |
| Sonnet 5.5 | $0.00008 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
docs-creating-accessible-diagrams 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Color Accessibility for Diagrams
This Skill provides guidance on creating accessible Mermaid diagrams using a verified color-blind friendly palette that meets WCAG AA standards. Use this when creating visual diagrams to ensure accessibility for all users, including those with color blindness (~300 million people worldwide).
Purpose
Use this Skill when:
- Creating Mermaid diagrams, flowcharts, or visualizations
- Working with color-dependent visual content
- Need to ensure WCAG compliance for diagrams
- Supporting users with color blindness (protanopia, deuteranopia, tritanopia)
- Choosing colors for documentation, diagrams, or UI components
Color Palette and Colors to Avoid
See Color Palette and Colors to Avoid for the full 8-color verified WCAG AA palette with hex codes and use cases, plus the colors that must never carry information (red, green, yellow, pink, magenta).
Core Accessibility Principles
See Core Accessibility Principles for the four principles — never rely on color alone, use color as enhancement, maintain WCAG AA contrast, and test for color blindness before publishing.
Mermaid Diagram Best Practices
See Mermaid Best Practices for the standard accessible Mermaid template, the ten essential Mermaid rules, comment syntax, and the special-character escaping table for node text and edge labels.
Common Mistakes and Testing Tools
See Common Mistakes and Testing Tools for the six most common accessibility mistakes with fixes, plus color blindness simulators and contrast checkers to verify diagrams before publishing.
Integration with Repository Conventions
This Skill integrates with:
- Color Accessibility Convention - Complete color accessibility standards
- Diagrams Convention - Mermaid diagram standards, comment syntax, special character escaping
- Content Quality Principles - Quality standards for all content including diagrams
What ships with it
7 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.
- 2d ago First seen · 73 lines · 41 tokens per session scan A e8647a7ea90d
docs-creating-accessible-diagrams is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 767 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
magic-ui
Use this skill when users want to add, customize, or troubleshoot Magic UI components in React/Next.js projects. It covers component selection, shadcn registry installation (@magicui/), integration patterns, and practical quality checks for accessibility and maintainability.
building-canvases
Create or edit a PostHog freeform canvas — a sandboxed browser application (data board, document, form, small tool, graphics experiment) stored in PostHog and rendered by the desktop/web app. Use when a task asks to build, generate, update, or fix a standalone canvas app, or when a freeform canvas id is given as the…
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
visualizing-change-over-time
Helps PostHog engineers and agents pick the right chart when a request is about visualizing change over time, before/after comparisons, or period-over-period movement while building UI with @posthog/quill-charts (dashboards, reports, the mcpanalytics frontend, custom visualizations). Use when a user asks how something…
opengeni-visualize
Create visualizations and interactive tools directly in conversation. Use when the user asks to see how something works, explore 'what happens when' or 'what changes', compare or inspect, or wants a simulation, map, chart, graph, or mockup, or when a visual clearly explains better than text. Use standard tools for…
quill-code
Edit the @posthog/quill design system locally and consume the change in products/desktop before it is published to npm. Use when changing quill components/primitives/tokens, when a quill change must be tested inside the Code app, or when the user mentions quill, the design system, the .local-quill tarball, or the…