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 dandacompany/bluekiwi --skill bk-versiongit clone --depth 1 https://github.com/dandacompany/bluekiwiWrote 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/dandacompany/bluekiwi/bk-version)<a href="https://agentmods.dev/skills/dandacompany/bluekiwi/bk-version"><img src="https://agentmods.dev/badge/skills/dandacompany/bluekiwi/bk-version.svg" alt="Measured on agentmods" 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.00068 | $0.00773 |
| Opus 5 | $0.00034 | $0.00387 |
| Sonnet 5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
bk-version 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 8d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asking questions across runtimes: wherever this skill says
AskUserQuestion, use your host runtime's native structured-question tool:AskUserQuestion(Claude Code),clarify(Hermes Agent),requestUserInput(Codex CLI),question(opencode). Always present the choices through that tool rather than plain prose. If the runtime has no such tool, list the options as numbered text and wait for the user's reply before proceeding.
BlueKiwi Version Management
View, compare, activate, and manage versions of a workflow family.
Argument Handling
/bk-version→ Select a workflow and show its version history./bk-version <workflow name>→ Load version history for the named workflow directly.
Core Concepts
- A workflow family shares the same root. All versions created via
create_new_version: trueare members of the same family. - Only one version per family can be active at a time. Activating a version automatically deactivates the previous active one.
- Inactive (archived) versions are readable but cannot be started with
start_workflow.
Execution Steps
Step 1: Select Workflow
If no argument, call list_workflows and ask via AskUserQuestion:
- header: "Which workflow?"
- options: workflow title list (up to 4)
Step 2: Load Version History
Call list_workflow_versions for the selected workflow ID.
Display the version list:
Workflow versions: {title}
━━━━━━━━━━━━━━━━━━━━━━━━━
v1.0 (ID: 12) ✅ Active created 2026-04-10
v1.1 (ID: 15) 🗄️ Archived created 2026-04-11
v2.0 (ID: 18) 🗄️ Archived created 2026-04-12
━━━━━━━━━━━━━━━━━━━━━━━━━
Active: v1.0
Step 3: Select Action
Ask via AskUserQuestion:
- header: "Version action"
- options: ["Activate a version", "Deactivate current", "Compare two versions", "Cancel"]
Action: Activate
Ask which version to activate via AskUserQuestion (show archived versions as options).
Confirm:
Activate v<x.y> (ID: <id>)?
This will deactivate the current active version v<current>.
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.
- 8d ago First seen · 104 lines · 68 tokens per session scan A 8e930f4fa600
bk-version is a skill published in the GitHub repository dandacompany/bluekiwi (23 stars, last pushed 1mo ago), licensed MIT. It adds 68 tokens to every session and 773 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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.