What is quinotospec-release?

A release workflow that bumps the version, consolidates changelogs, creates a Git tag, and publishes the result. A Git tag is a named marker for a particular code version.

Use it to classify changes as breaking, feature, or fix-level work, choose the version bump, update release records, tag the commit, and publish.

It turns release preparation into a documented sequence and checks that the project has the required files, changes, and clean working tree.

quinotospec-release — Skill for Claude Code and Codex by Quinoto-Tech

Install

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.

Any agent

npx skills add Quinoto-Tech/QuinotoSpec --skill quinotospec-release

Clone the repo

git clone --depth 1 https://github.com/Quinoto-Tech/QuinotoSpec

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-release/github.svg)](https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-release)

Your own site

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-release"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/quinoto-tech/quinotospec/quinotospec-release"><img src="https://agentmods.dev/badge/skills/quinoto-tech/quinotospec/quinotospec-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,297 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 pass 7 Sept 2026

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01297
Opus 5	$0.00000	$0.00648
Sonnet 5	$0.00000	$0.00259
Haiku 4.5	$0.00000	$0.00130

Measured 3d ago against content hash 14c4654bfc33, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

quinotospec-release 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 3d 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.

agent-dist/skills/quinotospec-release/SKILL.md · 108 lines

How it starts

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

Workflow: Release

Objetivo: automatizar el proceso de release de QuinotoSpec o de cualquier proyecto que use la metodología. Sigue el proceso documentado en CONTRIBUTING.md.

Precondiciones

Debe existir changelog (v1 en .quinoto-spec/quinoto-spec-changelog.md o v2 en .quinoto-spec/changelog/) con entradas desde el último release.
.version debe existir con la versión actual.
CHANGELOG.md (raíz del paquete QuinotoSpec) debe existir con entradas desde el último release.
Git debe estar disponible y el working tree limpio.

Paso 1 — Analizar cambios desde el último release

Buscar el último tag de git: git describe --tags --abbrev=0
Leer CHANGELOG.md (raíz) y .version del paquete QuinotoSpec.
Extraer todas las entradas posteriores a la fecha del último tag.
Si no hay tags previos, considerar todas las entradas del changelog.
Clasificar los cambios encontrados:

Tipo	Palabras clave en entradas	Bump
BREAKING	"breaking", "incompatible", "elimina", "migración"	Major
Feature	"nueva skill", "nuevo workflow", "nueva feature", "agrega"	Minor
Fix / Docs	"corrige", "fix", "documentación", "mejora"	Patch

Paso 2 — Determinar y confirmar version bump

Según la clasificación del paso 1, determinar el bump sugerido:
- Si hay al menos 1 BREAKING → Major
- Si hay al menos 1 Feature y 0 BREAKING → Minor
- Si solo hay Fix/Docs → Patch
Ejecutar quinotospec-norns --check para leer la versión actual (fuente canónica .version) y detectar drift preexistente entre .version, manifest.json, install.sh, README.md/README_EN.md, docs/ARCHITECTURE.md, CHANGELOG.md, V3_ROADMAP.md y scripts/validate-all.sh. Si reporta DRIFT, mostrarlo al usuario — el Paso 4 lo corrige, pero el usuario debe estar al tanto antes de confirmar.
Calcular la nueva versión aplicando el bump sugerido (semver) sobre la versión actual.

Mostrar al usuario:

Release Plan ──────────────────────────────
Versión actual:  {{CURRENT}}
Versión nueva:   {{NEW}} ({{BUMP_TYPE}})
Cambios:         {{N}} entradas de changelog
─────────────────────────────────────────────
¿Confirmás el release? (si/no)

Si el usuario responde "no", preguntar qué bump forzar: --bump major|minor|patch.

Read the full file on GitHub · 108 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.

3d ago Changed 14c4654bfc33
9d ago First seen · 108 lines · 0 tokens per session scan A 75b325cde16d

Subscribe to this mod's changes

quinotospec-release is a skill published in the GitHub repository Quinoto-Tech/QuinotoSpec (20 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,297 tokens. 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-09-03.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

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.

paperclipai/paperclip · 42 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

pack-submit

Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.

aeonfun/aeon · 27 tokens

updater_guide

Guidance for checking for and installing Row-Bot updates.

siddsachar/row-bot · 17 tokens