What is qalma-release?

A release guide for publishing Qalma packages, reusable JavaScript components and tools, to npm, the package registry for JavaScript projects.

Use it when preparing or troubleshooting releases of @qalma/editor, @qalma/skills, or @qalma/kit, including versioning, GitHub Actions, Nx, npm, and trusted publishing.

It reduces mistakes in version changes, release tags, automated publishing, and the credentials used by the release workflow.

qalma-release — Skill for Codex by cdskill/qalma

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/cdskill/qalma

agentmods

npx agentmods add skills/cdskill/qalma/qalma-release

Made for: 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/cdskill/qalma/qalma-release/github.svg)](https://agentmods.dev/skills/cdskill/qalma/qalma-release)

Your own site

<a href="https://agentmods.dev/skills/cdskill/qalma/qalma-release"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/qalma-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/cdskill/qalma/qalma-release"><img src="https://agentmods.dev/badge/skills/cdskill/qalma/qalma-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,311 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.

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.00057	$0.01311
Opus 5.5	$0.00023	$0.00524
Sonnet 5.5	$0.00011	$0.00262
Haiku 4.5	$0.00006	$0.00131

Measured 2mo ago against content hash d4ca860d382a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

qalma-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 2mo 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.

.agents/skills/qalma-release/SKILL.md · 105 lines

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.

Qalma Release

@qalma/editor, @qalma/skills, and @qalma/kit are published to npm under the latest dist-tag while the public API stabilizes. The packages are pre-1.0, but public releases use normal semver versions without prerelease suffixes. The scripted release path bumps the minor version on every release (0.2.0, 0.3.0, and so on).

Releases are tag-driven: a vX.Y.Z git tag pushed to main triggers GitHub Actions, which builds, re-derives the version from the tag, and publishes all three packages via npm's OIDC Trusted Publisher (no npm token in CI).

For the full architecture, history, and troubleshooting, read release-pipeline.md.

Cut a Release

Make sure main is clean and up to date (git status, git pull).
If the current version is still on the historical beta line, bootstrap the first normal semver release explicitly:
```
pnpm nx release 0.2.0 --skip-publish --dry-run
pnpm nx release 0.2.0 --skip-publish
node tools/sync-changelog-doc.mjs
```
This one explicit version is needed because Nx's native minor bump from 0.1.0-beta.4 resolves to 0.1.0, while Qalma's new policy is to move to the next minor without a suffix.
After 0.2.0, preview the next minor bump with pnpm release:dry-run.
After 0.2.0, run the normal release command with pnpm release.

For an explicit one-off version, call Nx directly so the version argument is passed before the changelog-sync command:
```
pnpm nx release <version> --skip-publish
node tools/sync-changelog-doc.mjs
```
These scripts or commands run nx release ... --skip-publish, then sync the generated editor changelog into the docs changelog. The release portion:
- Runs the preVersionCommand (./node_modules/.bin/nx run-many -t build -p editor skills ui-kit).
- Writes the new version into libs/editor/package.json and dist/libs/editor/package.json, libs/skills/package.json and dist/libs/skills/package.json, plus libs/ui-kit/package.json and dist/libs/ui-kit/package.json.
- Generates project changelogs from conventional commits.
- Commits the manifest and changelog change as chore(release): publish <version>.
- Creates an annotated tag v<version> on that commit.
- Skips publishing (CI does that).

Read the full file on GitHub · 105 lines

Files

What ships with it

2 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.

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.

2mo ago First seen · 105 lines · 57 tokens per session scan A d4ca860d382a

Subscribe to this mod's changes

qalma-release is a skill published in the GitHub repository cdskill/qalma (11 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 1,311 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-08-31.

Git and workflow Releases angular contenteditable editor headless prosemirror rich-text-editor

qalma-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
qalma-releasecdskill/qalma	Skill	11	yesterday	MIT	A	57	Codex
create-prmicrosoft/vscode	Skill	195k	yesterday	MIT	A	27	Claude Code, Codex
create-draft-prmicrosoft/vscode	Skill	195k	yesterday	MIT	A	31	Claude Code, Codex
release-versionvnotex/vnote	Skill	13k	yesterday	LGPL-3.0	A	86	Claude Code, Codex
releasing-weaverse-sdksWeaverse/weaverse	Skill	196	yesterday	MIT	A	70	Claude Code
shipping-and-launchloiane/specs-driven-development-spring-angular	Skill	62	yesterday	MIT	A	64	Claude Code
release-auditamirfish1/claude-command-center	Skill	216	yesterday	none	B	95	Claude Code