Borrowing it
Nothing to install: this file belongs to Luqueee/kivgraph. 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/Luqueee/kivgraph/main/.claude/skills/publishing-releases/SKILL.mdgit clone --depth 1 https://github.com/Luqueee/kivgraphWrote 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/luqueee/kivgraph/publishing-releases)<a href="https://agentmods.dev/skills/luqueee/kivgraph/publishing-releases"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/publishing-releases/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/luqueee/kivgraph/publishing-releases"><img src="https://agentmods.dev/badge/skills/luqueee/kivgraph/publishing-releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.04061 |
| Opus 5 | $0.00029 | $0.02031 |
| Sonnet 5 | $0.00012 | $0.00812 |
| Haiku 4.5 | $0.00006 | $0.00406 |
Grade A, and why
publishing-releases 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 4d 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 -fsS https://kivgraph.dev/releases/ | grep -F "vX.Y.Z" How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publicar una release de Kivgraph
Esta skill cubre el cambio completo: decidir si merece la pena publicar, actualizar las fuentes correctas, pasar los gates, crear el tag y comprobar lo que realmente llegó a GitHub y al MCP Registry. No publica nada si la persona no lo ha pedido explícitamente.
Reglas que no se negocian
- La versión sólo sube. Nunca se baja, se reinicia, se reutiliza ni se reescribe un tag que ya se haya empujado.
- Las releases estables usan vX.Y.Z. Las releases de desarrollo usan un sufijo SemVer, por ejemplo vX.Y.Z-dev.N; son prereleases y no se marcan como latest.
- El tag debe apuntar al commit exacto que ya está integrado en main. No se etiqueta una rama de trabajo ni un árbol sucio.
- La nota de release debe existir antes del tag. Si falta, CI quema el tiempo de construir los artefactos y falla justo antes de publicarlos.
- Una release es un evento de distribución, no una marca de progreso del backlog. El número de tarea, un PASS en TASKS.md o una suite verde no son por sí solos un motivo.
kivgraph update selecciona un canal y compara versiones con SemVer. El canal
stable consulta /releases/latest; el canal dev enumera las primeras 100
prereleases publicadas y elige la mayor versión válida. Sin --channel, una
instalación estable usa stable y una instalación prerelease usa dev. También
se puede seleccionar explícitamente con --channel stable|dev o
KIVGRAPH_UPDATE_CHANNEL.
1. Decidir si hay release y qué número usar
Publicar sólo tiene sentido si quien actualiza obtiene algo ejecutable y observable:
- una corrección que afecta al binario publicado;
- una capacidad nueva del CLI, MCP o de un lenguaje soportado;
- un cambio de compatibilidad, schema o migración;
- una corrección del bundle, instaladores, checksums, analizador o visor web.
No publicar por documentación aislada, TASKS.md, ADRs, benchmarks, tests, refactors sin cambio observable, ni por completar una tarea LUQUE-####. Resume en una frase qué gana quien actualiza. Si la frase sólo habla del trabajo interno, no hay release.
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.
- 4d ago Changed · +188 lines · -27 tokens per session 1b67cff16999
- 8d ago First seen · 214 lines · 85 tokens per session scan A c56d04631bd4
publishing-releases is a skill published in the GitHub repository Luqueee/kivgraph (19 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 4,061 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-31.
Other skills, from other repositories
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
pyo3-bindings
PyO3 conventions for exposing a Rust core to Python: pyclass/pymethods, PyErr/PyResult error mapping, GIL release, properties, maturin builds, and pytest. Load when generating or reviewing PyO3 Python bindings for a Rust library.
codestory-grounding
Use when an agent should ground a local repository with CodeStory before making source claims, planning edits, choosing tests, reviewing changes, or using broad retrieval evidence through the CodeStory plugin MCP.
vigilante-issue-implementation-on-go
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Go repository with idiomatic tooling and security guidance.