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 agentmods add skills/bitovi/convey/naming-guidenpx skills add bitovi/convey --skill naming-guidegit clone --depth 1 https://github.com/bitovi/conveyWrote 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/bitovi/convey/naming-guide)<a href="https://agentmods.dev/skills/bitovi/convey/naming-guide"><img src="https://agentmods.dev/badge/skills/bitovi/convey/naming-guide.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 | $0.00043 | $0.04151 |
| Opus 5 | $0.00022 | $0.02076 |
| Sonnet 5 | $0.00009 | $0.00830 |
| Haiku 4.5 | $0.00004 | $0.00415 |
Grade A, and why
naming-guide 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 5d 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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convey Naming Guide
Canonical names for every part of Convey, organized as a visual topology. Use these names in code comments, docs, specs, conversations, and prompts.
Path notation example: Panel > Design Tab > Box Model > Side Slots
Topology
Convey
├── Overlay
│ ├── Toggle Button
│ ├── Selection Mode
│ │ ├── Hover Outline
│ │ ├── Hover Tooltip
│ │ └── Highlight Overlay
│ ├── Element Toolbar
│ │ ├── Re-Select Button
│ │ ├── Draw Button
│ │ └── Select More Button
│ ├── Group Picker
│ │ ├── Exact Match Summary
│ │ ├── Similar Elements List
│ │ └── Highlight Preview
│ ├── Draw Popover
│ │ ├── Position Items
│ │ └── Screenshot & Annotate
│ ├── Toast Notification
│ ├── Drop Zone
│ │ ├── Cursor Label
│ │ ├── Drop Indicator
│ │ └── Arrow Indicators
│ └── Containers
│ ├── Modal
│ ├── Popover
│ ├── Sidebar
│ └── Popup
│
├── Panel
│ ├── Header
│ │ ├── Select Element Button
│ │ ├── Element Info
│ │ └── Container Switcher
│ ├── Tab Bar
│ ├── Design Tab
│ │ ├── Box Model
│ │ │ ├── Layer Rings
│ │ │ ├── Side Slots
│ │ │ ├── Corner Slots
│ │ │ ├── Shorthand Slot
│ │ │ └── Mini Scrubber
│ │ ├── Corner Model
│ │ │ ├── Center Slot
│ │ │ ├── Edge Slots
│ │ │ └── Corner Slots
│ │ ├── Property Sections
│ │ │ ├── Section Header
│ │ │ ├── Add Property Dropdown
│ │ │ ├── Scale Scrubber
│ │ │ ├── Class Chip
│ │ │ └── Empty State
│ │ ├── Color Grid
│ │ │ ├── Special Colors Row
│ │ │ ├── Hue Rows
│ │ │ └── Color Cell
│ │ ├── Flex Controls
│ │ │ ├── Flex Direction Select
│ │ │ ├── Flex Wrap Select
│ │ │ ├── Flex Justify Select
│ │ │ ├── Flex Align Select
│ │ │ └── Gap Model
│ │ ├── Gradient Editor
│ │ │ ├── Direction Picker
│ │ │ ├── Gradient Bar
│ │ │ └── Color Swatch
│ │ └── Shadow Editor
│ │ ├── Shadow Layer Row
│ │ └── Ghost Row
│ ├── Components Tab
│ │ ├── Component List
│ │ │ ├── Component Group Item
│ │ │ └── Armed State
│ │ ├── Loading State
│ │ └── Storybook Not Detected
│ ├── Message Tab
│ │ ├── Compose Area
│ │ │ ├── Microphone Button
│ │ │ └── Add Message Button
│ │ └── Staged Messages List
│ ├── Queue Footer
│ │ ├── Connection Status Warning
│ │ ├── No Agent Watching Warning
│ │ └── Patch Queue Popovers
│ │ ├── Draft Popover
│ │ ├── Committed Popover
│ │ ├── Implementing Popover
│ │ └── Implemented Popover
│ └── Design Mode
│ └── Design Canvas
│
├── Server
│ ├── Patch Queue
│ ├── MCP Tools
│ │ ├── implement_next_change
│ │ ├── get_next_change
│ │ ├── mark_change_implemented
│ │ ├── list_changes
│ │ └── discard_all_changes
│ ├── Tailwind Compiler
│ ├── Ghost Cache
│ └── WebSocket Hub
│
└── Storybook Addon
├── Addon Panel
├── Preview Decorator
└── Preset
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.
- 5d ago First seen · 271 lines · 43 tokens per session scan A 724fd1939c32
naming-guide is a skill published in the GitHub repository bitovi/convey (46 stars, last pushed 19d ago), licensed MIT. It adds 43 tokens to every session and 4,151 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-30.
Other skills, from other repositories
omh-accessibility-audit
This is a Hermes-native accessibility-audit workflow skill.
omh-design-quality-gate
This is a Hermes-native design-quality-gate workflow skill.
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).
presentation-deck
Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.
ux-writing
Write interface copy — microcopy, error messages, empty states, and CTAs. Use when the words are the deliverable. For content structure and ownership, use content-strategy (ux-strategy).