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/.cursor/skills/minor-release-highlights/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/minor-release-highlights)<a href="https://agentmods.dev/skills/dfirtnt/huntable-cti-studio/minor-release-highlights"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/minor-release-highlights/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/minor-release-highlights"><img src="https://agentmods.dev/badge/skills/dfirtnt/huntable-cti-studio/minor-release-highlights.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.01015 |
| Opus 5 | $0.00039 | $0.00508 |
| Sonnet 5 | $0.00015 | $0.00203 |
| Haiku 4.5 | $0.00008 | $0.00102 |
Grade A, and why
minor-release-highlights 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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minor / point release highlights
Scope (what this is)
- In scope: Themes that mark a line in the sand versus the previous minor (e.g.
2.4.xvs2.3.x): new workflows, expanded product surface, UX model shifts, defaults that change how people work. - Out of scope: Individual commits, PR laundry, long bugfix bullets, dependency bumps listed for their own sake, internal refactors unless they clearly change user capabilities.
Semver anchor: “Dot” often means patch (x.y.Z). Patch releases are usually fixes and small deltas; 2–3 major “feature set” themes are a better fit for minor (x.Y.0) or an intentional “small release” milestone. If the user is cutting only a patch, say so and offer either (a) one light “themes” paragraph only if the delta truly warrants it, or (b) a short “fixes and polish” framing instead of inventing false epics.
Best practices
- Compare to the last minor baseline — Establish the previous minor tag or
CHANGELOGsection forx.(Y-1).0(or agreed baseline). Everything you cite should be since that baseline, not “recent work.” - Exactly two or three themes — Fewer than two rarely earns a minor story; more than three dilutes the message. Each theme is a named capability story, not a bucket of tickets.
- User- or operator-visible — Prefer outcomes analysts, admins, or integrators experience (screens, APIs, workflows, limits, guarantees). Defer infra-only items unless they unlock a new class of use (e.g. “reliability for 24/7 schedules”).
- No fake major — Language should reflect meaningful but bounded change: not a rebranding, not “everything is new,” not deprecation of entire product lines unless that is true.
- Evidence over invention — Ground themes in merged changes, docs, CHANGELOG, or routes/UI you can point to. If evidence is thin, label proposals tentative and say what would confirm them.
- Name themes for scanning — Each theme: short title (3–8 words) + one paragraph (what changed, who it helps, why it matters) + optional examples (concrete screens, endpoints, or commands).
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.
- 12d ago First seen · 62 lines · 77 tokens per session scan A 9465f37dfe2a
minor-release-highlights is a skill published in the GitHub repository dfirtnt/Huntable-CTI-Studio (11 stars, last pushed 4d ago), licensed MIT. It adds 77 tokens to every session and 1,015 once invoked, about $0.0004 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…
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…
gsd-ship
Create PR, run review, and prepare for merge after verification passes.
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.