convey: Skill for Claude Code

.github/skills/mode-button-behavior/SKILL.md

mode-button-behavior is a skill for Claude Code, Codex from bitovi/convey. It costs 56 tokens per session (5,696 once invoked), scanned A, original, MIT.

A reference for how Convey's Select and Insert modes and its Place and Replace component buttons should behave. It describes the separate button systems, their states, labels, visible tabs, page interactions, and WebSocket syncing.

In plain words
What is it for?
Use it when changing button states, colors, labels, tab visibility, or page interactions. It also applies when changing how panel buttons, overlay buttons, and component placement or replacement buttons stay in sync.
Why use it?
It gives developers a shared model for button behavior before they change the interface. Reviewing and updating the documented flow tables helps prevent conflicting states between the panel, overlay toolbar, and component rows.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is bitovi/convey's own configuration. It tells Claude Code and Codex how to work on convey itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything convey configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bitovi/convey. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bitovi/convey/main/.github/skills/mode-button-behavior/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bitovi/convey

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for mode-button-behavior

README.md
[![agentmods](https://agentmods.dev/badge/skills/bitovi/convey/mode-button-behavior/github.svg)](https://agentmods.dev/skills/bitovi/convey/mode-button-behavior)
Your own site
<a href="https://agentmods.dev/skills/bitovi/convey/mode-button-behavior"><img src="https://agentmods.dev/badge/skills/bitovi/convey/mode-button-behavior/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.

agentmods 80×15 button for mode-button-behavior

Your own site · 80×15
<a href="https://agentmods.dev/skills/bitovi/convey/mode-button-behavior"><img src="https://agentmods.dev/badge/skills/bitovi/convey/mode-button-behavior.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,696 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Rogue Agent · line 343
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
  • high Rogue Agent · line 343
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.05696
Opus 5.5 $0.00022 $0.02278
Sonnet 5.5 $0.00011 $0.01139
Haiku 4.5 $0.00006 $0.00570

Measured 2mo ago against content hash 27c4230ed9b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mode-button-behavior 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 2mo 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.

.github/skills/mode-button-behavior/SKILL.md · 360 lines

How it starts

The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Mode & Component Button Behavior

Purpose

This skill documents the complete interaction flows for the global mode buttons and component row buttons. These two button systems work together but have independent state.

Before modifying any button behavior, tab visibility, or page interaction logic:

  1. Review the flow tables below
  2. Identify which flow(s) your change affects
  3. Update the tables to reflect the proposed new behavior
  4. Confirm the updated tables with the user
  5. Only then implement the change

Key Concepts

There are three button systems that stay in sync:

  • Panel mode buttons (top-left of panel): Select and Insert. These control which tab is visible AND whether the page has an active interaction (crosshair, hover outlines, browse indicators).
  • Overlay toolbar buttons (floating bar on the page, above selected element): Select, Insert, Design, Text, Replace, Place. These mirror the panel's mode and tab state. Clicking a button on either side syncs the other via WebSocket.
  • Component row buttons (inside the Place/Replace tab): One per component. These arm a specific component for placement or replacement.

The panel and overlay toolbars stay in sync bidirectionally:

  • Clicking a mode/tab button on the panel sends a message to the overlay, which rebuilds its toolbar to match.
  • Clicking a mode/tab button on the overlay sends a message to the panel, which updates its state to match.
  • The same state transitions apply regardless of which side the user clicks.

The panel mode buttons and overlay mode buttons do two orthogonal things that happen to be bundled together:

  1. Show a tab — make the Place or Replace tab visible so the user sees the component list
  2. Activate a page interaction — turn on the overlay's browse/crosshair mode

After a component is placed or replaced, the tab should stay visible but all page interactions stop and both buttons return to gray.

Button Colors

Panel mode buttons (Select, Insert)

Read the full file on GitHub · 360 lines

Changes

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.

  1. 2mo ago First seen · 360 lines · 56 tokens per session scan A 27c4230ed9b9

Subscribe to this mod's changes

mode-button-behavior is a skill published in the GitHub repository bitovi/convey (47 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 5,696 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-08-30.