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.
npx agentmods add skills/samilozturk/agentlint/release-workflownpx skills add samilozturk/agentlint --skill release-workflowgit clone --depth 1 https://github.com/samilozturk/agentlintWrote 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/samilozturk/agentlint/release-workflow)<a href="https://agentmods.dev/skills/samilozturk/agentlint/release-workflow"><img src="https://agentmods.dev/badge/skills/samilozturk/agentlint/release-workflow.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00069 | $0.00698 |
| Opus 5 | $0.00034 | $0.00349 |
| Sonnet 5 | $0.00014 | $0.00140 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
release-workflow 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Release Workflow
When to Use
Use this skill when:
- preparing a release-affecting change
- checking whether a changeset is required
- reviewing
release/nextflow correctness - validating package tag and publish expectations
Purpose
Apply the repository's documented release workflow consistently across CLI and MCP packages.
Scope
Included
- changesets
PUBLISH.mdandCONTRIBUTING.md- release scripts and package dry-runs
- package-scoped tag expectations
Excluded
- manual publish execution
- ad hoc versioning strategy changes
- git push, mirror, or pipeline debugging outside routine release flow
Inputs
change-summarytouched-pathspublished-surface-impactrelease-goal
Step-by-step Execution
- Read
PUBLISH.md,CONTRIBUTING.md, and impacted package files. - Determine whether the change affects a published package output.
- If yes, require a changeset; if no, explain why not.
- Verify root checks and package dry-run expectations.
- Confirm the expected GitLab release path and package-scoped tag pattern.
- Return a release checklist tailored to the touched files.
- Hand off Git or pipeline incidents to
git-release-ci-ops.
Output Contract
Return:
- changeset required: yes/no + why
- affected package(s)
- exact verification commands
- release path summary
- risks or drift to review
Verification Commands
pnpm run build
pnpm run release-status
pnpm run typecheck
pnpm run lint
pnpm run test
npm pack --dry-run --workspace packages/cli
npm pack --dry-run --workspace packages/mcp
Evidence Format
- touched package(s)
- changeset decision
- commands listed
- release step summary
- any process mismatch
Safety / DONTs
- Do not hand-edit package versions or changelogs generated by the release MR flow.
- Do not reintroduce dual publish automation.
- Do not treat GitHub as the publish control plane.
- Do not skip dry-runs when package metadata or release logic changes.
Gotchas
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.
- 5d ago First seen · 106 lines · 69 tokens per session scan A 10a7e745c931
release-workflow is a skill published in the GitHub repository samilozturk/agentlint (30 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 698 once invoked, about $0.0003 per session on Opus 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-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.
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.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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…