Borrowing it
Nothing to install: this file belongs to hachej/boring-ui. 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/hachej/boring-ui/main/.agents/skill-library/devops-cut-boring-ui-release/SKILL.mdgit clone --depth 1 https://github.com/hachej/boring-uiWrote 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/hachej/boring-ui/devops-cut-boring-ui-release)<a href="https://agentmods.dev/skills/hachej/boring-ui/devops-cut-boring-ui-release"><img src="https://agentmods.dev/badge/skills/hachej/boring-ui/devops-cut-boring-ui-release.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.1 | $0.00056 | $0.02530 |
| Opus 5 | $0.00028 | $0.01265 |
| Sonnet 5 | $0.00011 | $0.00506 |
| Haiku 4.5 | $0.00006 | $0.00253 |
Grade A, and why
devops-cut-boring-ui-release scanned grade A with 2 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
code=$(curl -s -o /dev/null -w '%{http_code}' -m 8 "$url" 2>/dev/null || echo 000) Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
node -p "require(require('child_process').execSync('npm root -g').toString().trim() + '/@hachej/boring-ui-cli/package.json').version" How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut boring-ui-v2 Release + Update Global CLI
Use this skill for one job: release the current main of boring-ui-v2 to npm via GitHub Releases, then install that exact CLI version globally on this machine.
Non-negotiables
- Work from
mainonly. - Do not overwrite or stash user/agent dirty work. If the current worktree is dirty or not on
main, create a clean temporary worktree. - Do not use destructive commands (
git reset --hard,git clean -fd, force push). - Do not run
boring-ui --versionas a version check: this CLI may start a server. Use package-manager metadata instead. - Do not install
@latestuntil npm confirms the new version is visible. - After installing the global CLI, restart already-running global
boring-uiservers; long-lived Node processes keep the old package code in memory. If the server is a systemd user service (boring-ui-workspaces.service), restart it withsystemctl --user restart— do notkill+nohupa systemd-managed process (it races the auto-restart). After restarting, wait until the workspace route serves HTTP 200 again before declaring the step done. - If any release workflow fails, stop and report the failed run URL.
1. Prepare a clean main worktree
From anywhere inside the repo:
git fetch origin main --tags
If the active worktree is clean and already on main:
git switch main
git merge --ff-only origin/main
If the active worktree is dirty or on another branch, use a temporary worktree instead:
release_dir=$(mktemp -d /tmp/boring-ui-v2-release.XXXXXX)
rmdir "$release_dir"
git update-ref refs/heads/main origin/main
git worktree add "$release_dir" main
cd "$release_dir"
Confirm release preconditions:
git status --short --branch
test "$(git branch --show-current)" = main
test "$(git rev-parse HEAD)" = "$(git rev-parse origin/main)"
2. Check the current and next package versions
before=$(node -p "require('./packages/cli/package.json').version")
echo "current CLI package version: $before"
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.
- 7d ago First seen · 252 lines · 56 tokens per session scan A b3ef8e2ed3ad
devops-cut-boring-ui-release is a skill published in the GitHub repository hachej/boring-ui (46 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,530 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 2 findings (makes network calls, runs shell commands). 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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.