Borrowing it
Nothing to install: this file belongs to malloydata/publisher. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/malloydata/publisher/main/.claude/skills/publisher-release/SKILL.mdgit clone --depth 1 https://github.com/malloydata/publisherWrote 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/malloydata/publisher/publisher-release)<a href="https://agentmods.dev/skills/malloydata/publisher/publisher-release"><img src="https://agentmods.dev/badge/skills/malloydata/publisher/publisher-release.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
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 →
- low Supply Chain · line 243 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00068 | $0.06748 |
| Opus 5 | $0.00034 | $0.03374 |
| Sonnet 5 | $0.00014 | $0.01350 |
| Haiku 4.5 | $0.00007 | $0.00675 |
Grade A, and why
publisher-release scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"$(curl -sS --max-time 20 https://pypi.org/pypi/malloy-publisher-sdk/json \ How it starts
The opening of the file, as written. The whole thing — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Releasing Publisher
A release is one workflow_dispatch of Release (NPM + Docker)
(.github/workflows/release.yml). Everything else in this skill exists because
work has to land on main before that dispatch, or be written after it
completes — and the step that is always skipped is the last one.
Read .github/workflows/CONTEXT.md (path from the repo root) before acting. It carries the publishing rules that are not guessable from the
YAML, and it is the authority when this file and it disagree.
Release notes: when to write one, and what number goes on it
RELEASE_NOTES.md is not written at release time. The PR that changes the
behaviour writes the note, in the same PR, as a ## [Unreleased] section —
which is the only way it gets written by someone who knows what changed. The
release then carries it to users on its own: gh-release appends every
[Unreleased] section to the release page, then pushes a branch stamping those
headings with the version that shipped them and prints a link to open it as a PR.
Writing the section is the whole job; opening and merging that PR is the one
thing the release cannot do for itself.
Does this change need one?
gh-release already attaches an auto-generated "What's Changed" list of merged
PRs. That list is sufficient for a routine patch, so a note is not a per-PR
chore. Write one when the PR list would leave a reader unable to act — when a
user or operator has to do something, or would otherwise draw a wrong
conclusion from an unchanged-looking system:
- A breaking change, or anything needing a migration step. Mark the heading
(BREAKING). - A new or removed API field, endpoint, or response shape — anything that breaks a strict generated client, or that consumers should move onto.
- A deprecation: what still works, for how long, and what to move to.
- Changed meaning of an existing signal — a metric label, a counter, an error code. A value that keeps its name and changes its basis is the case most worth writing, because nothing else will surface it.
- A silent failure that is now visible, or a bug whose symptom users have been living with. Say who was affected and how to tell.
- A new capability with a cost or a limit worth knowing before adopting it.
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.
- 8d ago First seen · 506 lines · 68 tokens per session scan A 988366e4318a
publisher-release is a skill published in the GitHub repository malloydata/publisher (100 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 6,748 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.
commit
Create git commits in the Unovis repo that pass its commitlint rules. Unovis uses a CUSTOM commit format (Type | Scope | Subscope: Sentence-case subject), NOT Conventional Commits, so feat:/fix: will be rejected by the commit-msg hook. Use this whenever staging and committing changes, writing or rewriting a commit…
open-pr
Open a pull request for the Unovis repo with the project's conventions — correct branch off main, the standard commit grouping, and the checklist-style PR body used by the maintainers. Use when asked to open/create/submit a pull request, prepare a branch for review, or write a PR description in this repository.
reimagine-it-extract
Emit the content signals reimagine-it reads from an HTML file — title, anchors, proper nouns, dates, numbers, emails, links, source hex colors, and the derived palette — as JSON without generating a redesign. Use when the user says /reimagine-it extract, "what does the engine see in this page", "extract the palette"…
reusable-visualization
Build ONE reusable chart visualization component that receives its data and its settings from the host application instead of fetching them, and declares the fields and config options the host exposes to viewers. Use this whenever a single chart component is reused across many different queries rather than built for…
lightdash-agent-slack-messaging
Use this skill when writing, designing, or generating Slack messages for Lightdash's in-app analytics agent. Triggers when someone asks to create agent update messages, Slack digests, agent notifications, weekly summaries, daily summaries, or any Slack copy for the Lightdash project agent. Also use when asked to vary…