Borrowing it
Nothing to install: this file belongs to juliakrivchikova/AccordAgents-desktop-app. 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/juliakrivchikova/AccordAgents-desktop-app/main/.agents/skills/release-beta/SKILL.mdgit clone --depth 1 https://github.com/juliakrivchikova/AccordAgents-desktop-appWrote 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/juliakrivchikova/accordagents-desktop-app/release-beta)<a href="https://agentmods.dev/skills/juliakrivchikova/accordagents-desktop-app/release-beta"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/release-beta/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/juliakrivchikova/accordagents-desktop-app/release-beta"><img src="https://agentmods.dev/badge/skills/juliakrivchikova/accordagents-desktop-app/release-beta.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.00059 | $0.01129 |
| Opus 5 | $0.00030 | $0.00564 |
| Sonnet 5 | $0.00012 | $0.00226 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
release-beta 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Beta
Treat npm run release:beta as release orchestration, not dependency installation. A release is complete only after the exact published ZIP passes dependency inspection and launches successfully.
Non-negotiable gates
- Release only the approved
maincommit. Confirm local and remotemainmatch. - Preserve unrelated user changes. Use a clean isolated clone when the primary checkout is dirty.
- In an isolated clone, run
npm ci. Never copy or symlinknode_modulesfrom another checkout. - Use native macOS arm64 Node. Do not release through Rosetta or an x64 Node binary.
- Run
npm run release:betaas one uninterrupted workflow. Do not replace it with individual build, tag, or upload commands. - Do not report success from typecheck, signing, notarization, or update-feed checks alone. They do not prove the packaged app can resolve runtime modules.
- Keep the dedicated CLI parity invariant intact: release only reviewed application behavior from
main; do not introduce release-only product behavior.
1. Prepare a real clean checkout
-
Record the approved commit and verify remote
mainpoints to it. -
If the active checkout contains staged, unstaged, or untracked user work, leave it untouched and create a temporary clean clone.
-
Before installing anything, select native arm64 Node and verify it:
node .agents/skills/release-beta/scripts/verify-release.mjs environmentEnsure
npmuses that same Node installation. This check must happen beforenpm ci; npm selects architecture-specific optional packages during installation. -
Install dependencies inside that checkout with
npm ciwhile the arm64 Node installation is first onPATH. -
Provide signing credentials through the normal environment or an ignored
.env.local. Never commit credentials. -
Run the deterministic dependency preflight:
node .agents/skills/release-beta/scripts/verify-release.mjs preflight
The preflight must confirm arm64 Node, a real local node_modules directory, the full locked production/development dependency tree, arm64-native optional packages, and local build binaries. Any failure is blocking.
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 · 101 lines · 59 tokens per session scan A 4b9a9fc08b73
release-beta is a skill published in the GitHub repository juliakrivchikova/AccordAgents-desktop-app (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,129 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-31.
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.