Borrowing it
Nothing to install: this file belongs to bablsoft/accessflow. 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/bablsoft/accessflow/main/.claude/skills/prep-gh-release/SKILL.mdgit clone --depth 1 https://github.com/bablsoft/accessflowWrote 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/bablsoft/accessflow/prep-gh-release)<a href="https://agentmods.dev/skills/bablsoft/accessflow/prep-gh-release"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/prep-gh-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/bablsoft/accessflow/prep-gh-release"><img src="https://agentmods.dev/badge/skills/bablsoft/accessflow/prep-gh-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 152 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 MCP Rug Pull · line 171 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00075 | $0.07428 |
| Opus 5.5 | $0.00030 | $0.02971 |
| Sonnet 5.5 | $0.00015 | $0.01486 |
| Haiku 4.5 | $0.00007 | $0.00743 |
Grade A, and why
prep-gh-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 1mo 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 — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare an AccessFlow release
You are preparing the AccessFlow repo for a tagged release. CLAUDE.md is the authoritative rulebook — re-read it before editing anything. This skill formalises the pre-release checklist that used to live in maintainers' heads: every roadmap item must be closed and documented and reflected on the marketing site, every admin-SPA screenshot must be regenerated against the current build, and only then may the milestone be flipped to "released".
The skill does not kick off the Release workflow itself — that stays an explicit maintainer action from the Actions tab (see docs/09-deployment.md → Cutting a release). This skill only prepares the repo so the workflow can run cleanly afterwards.
Inputs
The user passes a target semver, in any of these forms:
1.2v1.21.2.0
Normalize to:
vX.Yfor branch / PR naming (chore/release-prep-vX.Y,chore(release-prep): vX.Y).- The bare heading used in
docs/12-roadmap.md— e.g.## v1.2.
If the user omits the version, ask for it once and stop. Do not guess from the roadmap.
Project map
- Roadmap source of truth:
docs/12-roadmap.md. One## vX.Yheading per milestone, with an✅ releasedor🚧 in progressmarker, then bullet lines that reference(AF-NNN)issues. - Docs chapters (any feature must land in at least one of these):
docs/03-data-model.md— entities, columns, enums, indexesdocs/04-api-spec.md— REST + WebSocket specdocs/05-backend.md— proxy engine, workflow, AI, scheduled jobs, MCPdocs/06-frontend.md— pages, routing, storesdocs/07-security.md— auth, RBAC, encryptiondocs/08-notifications.md— channel types, payloads, retriesdocs/09-deployment.md— Docker / Helm / env vars / releasesdocs/13-mcp.md— MCP server
- README at the repo root — user-facing pitch, tech-stack versions, quick-start, project structure.
- Marketing site at
website/— static HTML/CSS/JS, no build step:website/index.html— landing page (pitch, supported DBs, AI providers, auth methods, feature tiles, roadmap section, quick-start, tech stack, docs grid, footer).website/docs/index.html— public operator docs (deployment, configuration entities, RBAC matrix, env vars).website/README.md— content-source map. Authoritative for "which app/docs source feeds which website section". Read it before judging website coverage.website/images/docs/— SPA screenshots, a light + dark pair for every page.website/changelog/index.html— the public changelog: one<section class="docs-section scroll-pad" id="vX-Y-0">per stable release, newest first, plus a TOC link per release. This skill is the only thing that writes a new entry (#836).website/version.json—{"version","released_at","changelog_url"}; every self-hosted install polls it daily and shows an update hint when it is newer than the running build. Stable releases only — never a-beta.N.website/sitemap.xml— every content edit above needs its<lastmod>bumped here too (websitePages.test.tspins it to the page's JSON-LDdateModified); the footer version-status sweep across the other pages does not (see 4b).
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.
- 1mo ago Changed dbe509dfb6fb
- 1mo ago Changed · +41 lines 359bea3e9760
- 2mo ago First seen · 361 lines · 75 tokens per session scan A a9b4bfd82e17
prep-gh-release is a skill published in the GitHub repository bablsoft/accessflow (11 stars, last pushed today), licensed Apache-2.0. It adds 75 tokens to every session and 7,428 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-31.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
operating-github-cli
Default GitHub skill for the action agent. Use githubcli for any GitHub request — create/list/view/close issues and PRs, assign, labels, repos, releases, checks, github.com/owner/repo URLs, or gh api. Prefer over shellrun/!gh. Run these with githubcli in the current agent turn.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
testdino-releases
Use when the user wants to browse, inspect, create, or update releases/milestones in a TestDino project. Covers listreleases, getrelease, createrelease, and updaterelease. Accepts counter-style IDs like MS-12.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.