Borrowing it
Nothing to install: this file belongs to luojiahai/code-by-wire. 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/luojiahai/code-by-wire/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/luojiahai/code-by-wireWrote 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/luojiahai/code-by-wire/release)<a href="https://agentmods.dev/skills/luojiahai/code-by-wire/release"><img src="https://agentmods.dev/badge/skills/luojiahai/code-by-wire/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/luojiahai/code-by-wire/release"><img src="https://agentmods.dev/badge/skills/luojiahai/code-by-wire/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 72 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 173 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
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.00082 | $0.04951 |
| Opus 5.5 | $0.00033 | $0.01980 |
| Sonnet 5.5 | $0.00016 | $0.00990 |
| Haiku 4.5 | $0.00008 | $0.00495 |
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 14d 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 — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
The maintainer drives releases in two phases, keyed off repo state. With the automation checkpoint below, one run can carry straight through both without stopping in between — pick the starting phase from what they asked and the repo state, then keep going as far as they authorize.
- Phase 1 — "bump version": the bump/changelog/PR are not on
mainyet. - Phase 2 — "release it": the bump PR has merged to
main; now tag and ship.
package.json version is the source of truth; the tag is v + that exact
string. CI internals, the botched-release runbook, and platform/signing notes
live at the end of this skill.
Orient first
Two things to settle before touching anything, especially on a bare /release
with no phase named.
Which phase? Compare the working version to the latest tag:
node -p "require('./package.json').version" # e.g. 0.1.5
git tag --sort=-v:refname | head -1 # e.g. v0.1.4
Version equals the latest tag → the last release shipped and nothing is
pending → Phase 1 (cut the next version). Version is ahead of the latest
tag → a bump already merged but isn't tagged → Phase 2 (tag and ship). When
unsure, git log --oneline --first-parent vLAST..HEAD shows what's unreleased.
gh defaults to the wrong host. This repo lives on personal GitHub, but gh
defaults to the work host, so every gh call needs both the host and the repo:
GH_HOST=github.com gh <cmd> -R luojiahai/code-by-wire ...
Plain git push/git tag are fine — only gh needs the prefix.
How far to take it
Merging, tagging, and publishing are each hard to reverse or visible to others, so they still deserve a deliberate go-ahead — but asking for that go-ahead three separate times, in three separate messages ("merge", then later "release it", then later "publish"), is pure friction when the maintainer already knows how far they want this to go. Collapse it: right after orienting, before touching anything, ask once via AskUserQuestion how far to drive this release. Scope the options to what's actually left from the phase you're starting in:
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.
- 14d ago Changed 9fdd99a84ae3
- 1mo ago First seen · 353 lines · 82 tokens per session scan A c5192d9c22cb
release is a skill published in the GitHub repository luojiahai/code-by-wire (73 stars, last pushed 15d ago), licensed MIT. It adds 82 tokens to every session and 4,951 once invoked, about $0.0003 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-30.
Other skills, from other repositories
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
github
A guide to using GitHub CLI, a command-line tool for working with GitHub repositories. It covers issues, pull requests, releases, labels, milestones, and workflow runs.
git-release-manager
Use when the user explicitly asks to prepare, tag, publish, push, or audit a Git release. Inspect branch, worktree, version metadata, changelog, tests, and release artifacts first, obtain confirmation for irreversible release actions, and record a recovery path.
update-skills
Create or update repository skills and instructions when major learnings are discovered during a session. Use when the user says "learn!", when a significant pattern or pitfall is identified, or when reusable domain knowledge should be captured for future sessions.