Borrowing it
Nothing to install: this file belongs to FilipeJesus/lanes. 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/FilipeJesus/lanes/main/.agents/skills/lanes-release/SKILL.mdgit clone --depth 1 https://github.com/FilipeJesus/lanesWrote 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/filipejesus/lanes/lanes-release)<a href="https://agentmods.dev/skills/filipejesus/lanes/lanes-release"><img src="https://agentmods.dev/badge/skills/filipejesus/lanes/lanes-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.
<a href="https://agentmods.dev/skills/filipejesus/lanes/lanes-release"><img src="https://agentmods.dev/badge/skills/filipejesus/lanes/lanes-release.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00044 | $0.01706 |
| Opus 5.5 | $0.00018 | $0.00682 |
| Sonnet 5.5 | $0.00009 | $0.00341 |
| Haiku 4.5 | $0.00004 | $0.00171 |
Grade A, and why
lanes-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 11d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Lanes through GitHub Actions
Use the authenticated GitHub CLI for FilipeJesus/lanes. Read the repository's
AGENTS.md and current workflow definitions before acting; the workflows may
have changed since this procedure was recorded.
Carry out the release stages the user requested. An end-to-end release includes preparation, review, normal approval and merge, publishing, and verification. Do not ask again for actions already authorized by that request. Creating or inspecting this skill does not authorize a release.
Never run scripts/release.sh, including npm run release or its aliases.
Use remote workflows and keep unrelated local changes out of the release.
Establish the target and current state
Set REPO=FilipeJesus/lanes; derive TARGET_VERSION from the user's request.
Check remote main's commit and package version, existing release PRs, tags,
releases, and recent CI/release runs. Use --repo "$REPO" on CLI commands and
repository-qualified API endpoints.
Read these files from GitHub at main, rather than assuming a local checkout
matches the remote:
.github/workflows/prepare-release.yml.github/workflows/auto-tag-release.yml.github/workflows/release.yml.github/workflows/ci.ymlpackage.jsonand, when reviewing preparation,package-lock.json
For example:
gh api "repos/$REPO/branches/main" --jq '.commit.sha'
gh api "repos/$REPO/contents/package.json?ref=main" --jq '.content | @base64d | fromjson | .version'
gh release list --repo "$REPO" --limit 6
gh pr list --repo "$REPO" --state open
gh run list --repo "$REPO" --branch main --limit 10
gh api "repos/$REPO/git/matching-refs/tags/v$TARGET_VERSION" --jq '.[].ref'
Match tag names exactly: the matching-refs API can also return longer names
sharing the prefix. A shallow checkout's git rev-parse is not proof that a
remote tag is absent.
The current preparation workflow accepts a single patch, minor, or major
bump. Confirm its result will equal the requested version before dispatching.
If main already has that version, reuse existing preparation and skip another
bump. Reuse an existing matching PR or in-progress run rather than duplicating it.
If the requested version cannot be produced by the workflow, resolve that
mismatch before changing anything.
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.
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.
- 11d ago First seen · 168 lines · 44 tokens per session scan A 447c05ee83b7
lanes-release is a skill published in the GitHub repository FilipeJesus/lanes (11 stars, last pushed 11d ago), licensed MIT. It adds 44 tokens to every session and 1,706 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-10-19.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
xberg-release
Xberg release on top of the shared release-workflow: mise run version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…