Borrowing it
Nothing to install: this file belongs to vinilana/invokta. 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/vinilana/invokta/main/.agents/skills/prepare-invokta-release/SKILL.mdgit clone --depth 1 https://github.com/vinilana/invoktaWrote 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/vinilana/invokta/prepare-invokta-release)<a href="https://agentmods.dev/skills/vinilana/invokta/prepare-invokta-release"><img src="https://agentmods.dev/badge/skills/vinilana/invokta/prepare-invokta-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/vinilana/invokta/prepare-invokta-release"><img src="https://agentmods.dev/badge/skills/vinilana/invokta/prepare-invokta-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Agent Snooping · line 10 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00982 |
| Opus 5 | $0.00030 | $0.00491 |
| Sonnet 5 | $0.00012 | $0.00196 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
prepare-invokta-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 9d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare an Invokta Release
Establish the release branch
- Read
.agents/skills/invokta-delivery/SKILL.md,docs/README.md, the release gates indocs/implementation-plan-and-acceptance-criteria.md, and the ADRs represented by the unreleased changes. - Inspect the working tree, current branch, local and remote mainline refs,
recent tags,
CHANGELOG.md, and commits since the latest release. Preserve unrelated changes and stop if they make the release slice ambiguous. - Select the next semantic version from the compatibility of the Unreleased changes and the repository's prior release policy. Request a decision when the correct increment is ambiguous.
- Confirm the intended mainline base. If local
mainandorigin/maindiverge, resolve the base explicitly before continuing. - Create or switch to
chore/release-X.Y.Zfrom the confirmed mainline before editing any release file. Never prepare or commit a release onmain.
Synchronize release metadata
- Bump the root version and every public package version to
X.Y.Z. - Bump every exact internal
@invokta/*dependency pin in public packages and examples. Update version assertions and protocol client self-identification constants that intentionally track the release. - Search the repository for the previous version. Classify every match as current release metadata, historical release documentation, or an unrelated dependency before changing it.
- Synchronize committed example lockfiles. For unpublished Invokta packages,
derive integrity values from the exact locally packed
X.Y.Zartifacts; never retain old integrity hashes or invent new ones. Recheck the hashes if package contents change afterward. - Move the Unreleased notes under
## [X.Y.Z] - YYYY-MM-DD, update the Unreleased comparison base, and add the release link. Preserve historical entries and write all release content in English. - Refresh
docs/validation-record.mdonly with evidence produced during this release run, including the review date, accepted ADRs, test totals, coverage, and audit count.
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.
- 9d ago First seen · 89 lines · 59 tokens per session scan A 6d5a9931fc43
prepare-invokta-release is a skill published in the GitHub repository vinilana/invokta (128 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 982 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-30.
Other skills, from other repositories
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.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.