OpenTag connects Slack with coding agents running on a computer controlled by the user, so channel mentions can queue work and return status, decisions, and evidence in the same thread. It is for engineering teams that want to run agents such as Claude Code, Codex, or Cursor against local checkouts through the Agent Client Protocol.
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 amplifthq/opentag --skill 4git clone --depth 1 https://github.com/amplifthq/opentagWrote 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/amplifthq/opentag/4)<a href="https://agentmods.dev/skills/amplifthq/opentag/4"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/4/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/amplifthq/opentag/4"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/4.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.00039 | $0.00813 |
| Opus 5.5 | $0.00016 | $0.00325 |
| Sonnet 5.5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
openmeld-cli 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.
This is a copy
100% identical to openmeld-cli — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenMeld CLI
Read this entry first, then only the topic needed for the current task. The local installed copy is maintained by OpenMeld. If it is unavailable, read the public entry. Reading this guide needs no login or installation. Running its commands needs OpenMeld CLI and the appropriate account access.
Choose one topic
- Read a Space, its history, members, or Wake progress
- Send, join, invite, use Files, Wake, stop, or publish a Wake reply
- Sign in, set up, connect, or recover this computer
- Look up exact command syntax
- Resolve the acting Profile, output view, copied URL, or saved state
Follow these relative links from the current local folder or public URL.
Do not preload every file. Use openmeld <command> --help for a missing flag.
This guide requires CLI 0.3.217 or later. A guide cannot add commands to an older
CLI; check openmeld --version before relying on a newly documented command.
Identity and ownership
A Space is the shared conversation. An Agent Profile is the AI teammate. OpenMeld Service runs local work; a running Service alone does not prove that an Agent is available or that a reply reached the Space.
--profile selects who acts. --view agent selects structured output.
Use the user's Human Profile when acting for the user; use the named Agent
Profile when that teammate should speak. Never invent IDs or credentials.
Keep one acting Profile for a workflow. For a single read, use an explicit
--profile or the copied Space URL; do not change the persistent default.
To add the current Codex or Claude Code session as a teammate, read the Space
operations topic and use openmeld space add-me. Do not search all Profiles
for a guessed match or invent a controller session ID.
Inside a Wake
Follow the current dispatch's action instructions. Publish through its
OpenMeld Space Action tool. If that tool is unavailable, use the exact
dispatch-owned CLI command printed in the task, including its executable path.
Do not substitute openmeld space send for the final Wake reply.
An action error is an error: preserve it. Ordinary terminal output is not a
Space reply. Verify that the Space received the visible outcome.
What ships with it
5 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 · 71 lines · 39 tokens per session scan A 1743a6d380b3
openmeld-cli is a skill published in the GitHub repository amplifthq/opentag (0 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 813 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to openmeld-cli, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
subagent-manager
A recipe for building a model of a user's preferences from an AI agent's conversation logs. It organizes decisions and outcomes into files that can inform memory, rules, or system prompts.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
index-refresh
Use when an LLM Wiki operation issue requests an index refresh. Rebuild wiki/index.md from the actual wiki tree, reconcile missing/deleted entries, and log counts without editing page bodies.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.