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 openmeld-changeloggit 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/openmeld-changelog)<a href="https://agentmods.dev/skills/amplifthq/opentag/openmeld-changelog"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/openmeld-changelog/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/openmeld-changelog"><img src="https://agentmods.dev/badge/skills/amplifthq/opentag/openmeld-changelog.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.00053 | $0.00818 |
| Opus 5.5 | $0.00021 | $0.00327 |
| Sonnet 5.5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
openmeld-changelog 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenMeld Changelog
Keep changelog/entries/*.md as the human- and agent-authored source of truth.
Treat CHANGELOG.md, changelog/index.json, and changelog/releases/*.md as
generated projections. Read developing/engineering/changelog.md before
editing either source or projections.
Choose the job
- Record a change: inspect the implementation and add one concise draft entry when users or contributors gain, lose, or materially experience a capability.
- Publish a change: add
publishedAt, optionalrelease, and concreteevidenceonly after the delivery claim is proven. - Backfill history: reconstruct an omitted entry from tags, commits, pull requests, tests, deployment records, or other durable evidence. Use the original availability date, not today's date.
- Prepare release notes: publish the applicable entries, rebuild the projections, and hand the generated release file to the authorized release workflow. A notes file is not release authorization.
Gather evidence
Use the coding agent's native file, Git, GitHub, test, and search tools. No custom Changelog command is required for investigation or writing.
Establish these facts separately:
- what behavior changed;
- who can notice or use it;
- which code, pull request, or commit contains it;
- whether it was merged;
- whether the relevant component was delivered; and
- whether any required real-user smoke produced the visible outcome.
Merge, tag, deployment, and smoke are different claims. Keep an entry draft when the evidence proves only an earlier claim.
Decide whether to record it
Record changes that affect users, operators, integrators, or contributors:
- new or removed capabilities;
- material workflow or behavior improvements;
- user-visible fixes and security changes;
- breaking behavior and deprecations; or
- developer-facing changes that alter supported integration or contribution work.
Skip internal refactors, test-only changes, routine dependency maintenance, and documentation cleanup when they do not change an external workflow. Combine several implementation commits into one user-meaningful entry when they deliver one outcome.
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.
- 2d ago First seen · 105 lines · 53 tokens per session scan A 6b480228ad11
openmeld-changelog is a skill published in the GitHub repository amplifthq/opentag (0 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 818 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-15.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-credit-harvest
Harvest one community PR into a release branch with authorship and credit preserved, verified green, and a warm thank-you.
github
Skill "github" from Hmbown/Codewhale, covering github, when to use, setup, workflow and non-goals.
release
Skill "release" from Hmbown/Codewhale, covering release, invocation, non-goals and workflow.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.