agentmods.dev

release

A release checklist and procedure for clawops, a TypeScript deployment tool. It covers testing, type checking, linting, version changes, and publishing packages to npm.

In plain words
What is it for?
Use it to prepare, review, and publish a clawops release, including its emergency manual publishing path.
Why use it?
It reduces missed checks and helps ensure that user-visible changes are versioned and published through the project's expected process.

Skill for Claude CodeCodex

1 1mo ago A scan 0 tokens original MPL-2.0
View the source file dfridkin/clawops
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.

agentmods
npx agentmods add skills/dfridkin/clawops/release
Any agent
npx skills add dfridkin/clawops --skill release
Clone the repo
git clone --depth 1 https://github.com/dfridkin/clawops

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00301
Opus 5 $0.00000 $0.00151
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured 2d ago against content hash e6b7857195a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/skills/release/SKILL.md · 39 lines

What it actually says

/release

Cut a clawops release.

Pre-flight checklist

  1. All tests pass: pnpm test
  2. No typecheck errors: pnpm typecheck
  3. Lint clean: pnpm lint
  4. Generated files current: pnpm gen:schemas --check
  5. All commits follow conventional format (feat, fix, docs, refactor, chore, test, perf, ci)
  6. A changeset exists for every user-visible change: ls .changeset/*.md

Steps

  1. Create changeset (if not already done): pnpm changeset

  2. Open the Version Packages PR: Push to main — the release.yml workflow will automatically create or update a "Version Packages" PR that bumps package.json and CHANGELOG.md.

  3. Review and merge the Version Packages PR.

  4. Workflow publishes to npm with provenance automatically on merge.

Manual publish (emergency only)

pnpm build
pnpm changeset version
pnpm release    # calls: changeset publish --provenance

Notes

  • Publishing requires NPM_TOKEN in GitHub Secrets.
  • Provenance is enabled via id-token: write permission in release.yml.
  • Never force-push main after a release tag is created.
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.

  1. 2d ago First seen · 39 lines · 0 tokens per session scan A e6b7857195a6

Subscribe to this mod's changes

release is a skill published in the GitHub repository dfridkin/clawops (1 stars, last pushed 1mo ago), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 301 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-08-31.

DevOps and cloudGit and workflowReleases
Related

Other skills, from other repositories

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 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

Draft concise release notes.

ollama/ollama · 9 tokens

greptimedb-release

Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).

GreptimeTeam/greptimedb · 75 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens