Borrowing it
Nothing to install: this file belongs to dfirtnt/Huntable-CTI-Studio. 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/dfirtnt/Huntable-CTI-Studio/main/.claude/skills/cut-release/SKILL.mdgit clone --depth 1 https://github.com/dfirtnt/Huntable-CTI-StudioWrote 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/dfirtnt/huntable-cti-studio/cut-release)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/cut-release"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/cut-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/dfirtnt/huntable-cti-studio/cut-release"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/cut-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Tool Misuse · line 194 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 288 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00136 | $0.02891 |
| Opus 5 | $0.00068 | $0.01445 |
| Sonnet 5 | $0.00027 | $0.00578 |
| Haiku 4.5 | $0.00014 | $0.00289 |
Grade A, and why
cut-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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cut Release
Walks the operator through the release flow documented in AGENTS.md
(sections "Release branch protection" and "Release tagging convention").
Those sections are authoritative; this skill automates the mechanics and
enforces the checkpoints.
Core invariants
Hold these in mind throughout:
mainis read-only between releases via GitHub branch protection (lock_branch,enforce_admins, no force push, no deletions). Feature work lives on the release branch — the codename/version-named line, currentlyeuropa-dev(scripts/release_cut.pyaccepts any branch matchingeuropa-*or the historicaldev-europa*, and rejects anything else).mainonly moves during release cuts.- Canonical tag format is
vMAJOR.MINOR.PATCHonly. The codename lives in the annotated tag message and the CHANGELOG heading, never in the tag name. pyproject.toml[project].versionis the single source of truth. Everything else mirrors it.- Never push silently. Every network-side-effect step (unlock, push the release branch, push tag, relock) gets an explicit operator confirm.
Phase 1: Gather release parameters
Ask the operator for three things. Confirm all three before touching anything.
-
Version in
MAJOR.MINOR.PATCHform. Read the current version frompyproject.toml[project].versionand help decide the bump type:- Patch (
5.3.0 -> 5.3.1): bug fixes only. - Minor (
5.3.0 -> 5.4.0): new features, backward compatible. - Major (
5.3.0 -> 6.0.0): breaking changes or significant architectural shift.
- Patch (
-
Codename:
- Major bump: pick a new planetary moon. Show the operator the
"Available Planetary Moon Names" section in
docs/reference/versioning.md, and exclude names already used in the Version History block (historically: Callisto, Ganymede, Kepler, Copernicus, Tycho). Good fresh candidates: Triton, Europa, Io, Titan, Enceladus. - Minor or patch bump: reuse the current codename. Read it from the
first line under
## Current Versionindocs/reference/versioning.md.
- Major bump: pick a new planetary moon. Show the operator the
"Available Planetary Moon Names" section in
What ships with it
1 file 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 · 308 lines · 136 tokens per session scan A 2c0891e91ba5
cut-release is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 3d ago), licensed MIT. It adds 136 tokens to every session and 2,891 once invoked, about $0.0007 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-30.
Other skills, from other repositories
configuring-windows-event-logging-for-detection
Configures Windows Event Logging with advanced audit policies to generate high-fidelity security events for threat detection and forensic investigation. Use when enabling audit policies for logon events, process creation, privilege use, and object access to feed SIEM detection rules. Activates for requests involving…
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
automating-devops
DevOps knowledge reference covering Git workflows, testing strategies, DevSecOps, release pipeline orchestration (release.yml, multi-arch images, cosign integration), CI/CD pipelines, database management, observability, and performance optimization. Use when working with Git, CI/CD, release pipelines, ghcr image…
os-release
A release checklist for publishing a new version of AI Team OS. It covers checks, synchronized version updates, bilingual release notes, builds, commits, tags, repository pushes, and GitHub release records.
release-publish
Pre-publish and publish path for crates.io, npm installer, GitHub Releases, SBOM. Use when cutting versions, editing release.yml, or adding publish steps. Never publish from a feature branch.
synthetic-release-notes
Draft release notes from user-provided changes.