Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add IngvarConsulting/unica --skill release-supportgit clone --depth 1 https://github.com/IngvarConsulting/unicaWrote 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/ingvarconsulting/unica/release-support)<a href="https://agentmods.dev/skills/ingvarconsulting/unica/release-support"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/release-support/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/ingvarconsulting/unica/release-support"><img src="https://agentmods.dev/badge/skills/ingvarconsulting/unica/release-support.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.00049 | $0.01322 |
| Opus 5.5 | $0.00020 | $0.00529 |
| Sonnet 5.5 | $0.00010 | $0.00264 |
| Haiku 4.5 | $0.00005 | $0.00132 |
Grade A, and why
release-support 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 15d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 15d ago Changed · +3 lines f72e1df653ed
- 16d ago Changed · +1 lines 622c35e1d0b7
- 19d ago Changed · +2 lines a294041b7a4b
- 28d ago Changed · +2 lines e504c4534e8d
- 1mo ago Changed · +20 lines 1bba474612d3
- 1mo ago Changed · -3 lines fc77134177a7
- 1mo ago Changed 145e5e616339
- 1mo ago Changed b9bb49a46cf4
- 1mo ago First seen · 53 lines · 49 tokens per session scan A 04ad6e791c8f
release-support is a skill published in the GitHub repository IngvarConsulting/unica (230 stars, last pushed today), with no licence file. It adds 49 tokens to every session and 1,322 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
bump-version
A procedure for changing a package and plugin version in several project files at the same time.
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
release
Only when asked to prepare a release, or when a project check requires release file sync.
ship
Run Consult's guarded maintainer flow for commit, merge, version bump, validation, and push.