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 yonatangross/orchestkit --skill ork-glyphgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/ork-glyph)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/ork-glyph"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/ork-glyph/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/yonatangross/orchestkit/ork-glyph"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/ork-glyph.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.00065 | $0.00899 |
| Opus 5.5 | $0.00026 | $0.00360 |
| Sonnet 5.5 | $0.00013 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
ork-glyph 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 26d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ork Glyph
Render immediately from the user's topic. With no topic, use the current conversation. Choose the form yourself without setup questions, task creation, or subagents. The inline rendering itself needs no external tools.
Encode information in structure. State the verdict in one prose line, then draw one render in a monospace code block. Follow it with two or three short observations when the diagram reveals something worth explaining.
Choose the form
| Data shape | Render |
|---|---|
| Inventory, audit, budget | Header meter, sections, rows, totals, caveats |
| Status, progress, health | Status box and bar meters |
| Options, trade-offs | Comparison table |
| Steps, pipeline, handoffs | Flow with arrows |
| Containment, layers | Nested boxes or tree |
| Ranking, scores, counts | Table and bars |
| Change over time | Sparkline or milestone track |
Rendering contract
- One render per reply, at most about 50 lines. In a terminal, keep each line within 76 display cells. In chat, web transcripts, and other non-TTY surfaces, use at most 72 cells and one narrow table or a vertical list, never side-by-side boards. Default to the non-TTY layout when the surface is uncertain.
- Use one box style per render:
┌─┐│└─┘normally,╭─╮│╰─╯for soft status cards, or+-|for ASCII-only surfaces. Keep nesting to three levels. Use arrows→,↓, or->and meters▓▓▓░░with the numeric value beside them. - Pair every status icon with a word: ✅ done, ❌ failed, ⚠️ warning, 🔄 in progress, ⏸ waiting, 💡 idea, 🚨 hard block, 🎯 goal, 🔥 top priority, 📜 doc, 🤖 agent, ⚡ hook, ℹ️ caveat. Risk uses 🟢 low, 🟡 medium, 🔴 high; ranking uses 🥇 1st, 🥈 2nd, 🥉 3rd.
- For domain rows, use at most one leading icon: 🐳 docker, 🌐 browser, 📦 package, 🐍 python, 🧠 model, 📱 device, 💾 volume, 🗑️ trash, 🗂️ files, 📥 downloads, 🔑 secret, 🧪 test, 🖥️ host, ☁️ cloud, 📧 mail, 💬 chat. Keep icons out of prose sentences and avoid emoji chains.
- Align labels and numbers by display width, accounting for wide characters. Avoid full-width decorative rules, em or en dashes, and Mermaid in this inline mode.
- Use only supplied or verified data. Print
?for unknown values. Show units, denominators, and arithmetic for totals; call out overlaps or estimates. - An inventory proceeds from subject and headline meter to labeled sections, then rows containing label, bar, value, and action when relevant. Finish with section totals, the overall arithmetic, and caveats. Omit unsupported fields.
What ships with it
1 file 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.
- 26d ago First seen · 69 lines · 65 tokens per session scan A 91aa1ba3a06b
ork-glyph is a skill published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 899 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-09-20.
Other skills, from other repositories
cocosketch
Generate visual draw.io diagrams from CocoPlus artifacts via a deterministic seven-step pipeline.
decocms-ui
Build or style React UI with the decocms product design system (@decocms/ui). Use when creating interfaces, pages, or components in a project that should look like decocms products, when the user mentions "design system", "@decocms/ui", "decocms style", or asks to make UI consistent with Studio. Covers installation…
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
bento-slides
Use when creating or editing Bento (.bento.html) slide decks, including any request for a single-file HTML slide deck.
mermaid-diagrams
Use the mermaid-diagrams skill whenever you are creating or updating mermaid diagrams. Provides guidance on mermaid best practices.