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-reportgit 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-report)<a href="https://agentmods.dev/skills/dandacompany/bluekiwi/bk-report"><img src="https://agentmods.dev/badge/skills/dandacompany/bluekiwi/bk-report/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/dandacompany/bluekiwi/bk-report"><img src="https://agentmods.dev/badge/skills/dandacompany/bluekiwi/bk-report.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.00067 | $0.00892 |
| Opus 5 | $0.00034 | $0.00446 |
| Sonnet 5 | $0.00013 | $0.00178 |
| Haiku 4.5 | $0.00007 | $0.00089 |
Grade A, and why
bk-report 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 — 128 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 Task Report
Generate a structured summary report of a completed or in-progress task.
Argument Handling
/bk-report→ Report on the most recent active or completed task./bk-report <task_id>→ Report on the specified task.
Execution Steps
Step 1: Load Task Data
Call advance with peek: true to get the current task state and task_context.
If a specific task_id is provided, use it directly.
task_context.artifacts already contains the full artifact list for the task (file paths, git refs, URLs that were recorded via execute_step's artifacts[] array). No separate load call is needed.
Step 2: Load Findings
If the workflow includes compliance steps, call list_findings to retrieve compliance findings. Otherwise skip this step.
Step 3: Generate Report
Build the report from the collected data:
# Task Report: {workflow title}
**Task ID**: {id}
**Status**: {running | completed | failed}
**Started**: {started_at}
**Completed**: {completed_at or "in progress"}
**Steps**: {completed}/{total}
---
## Summary
{task_context.running_context summary — key decisions and outcomes}
---
## Step-by-Step Log
| Step | Title | Status | Key Output |
| ---- | ------------ | ------ | ---------------------------- |
| 1 | Clarify Goal | ✅ | Defined target market as SMB |
| 2 | Collect Data | ✅ | 15 competitors identified |
| 3 | Review | ⏳ | Pending approval |
---
## VS Responses
{for each step with web_response data}
### Step {N}: {title}
{format the JSON response as readable text}
- **Selected**: {selections joined with ", "}
- **Values**: {key = value for each entry in values}
- **Priority ranking**: {ranking as numbered list}
- **Matrix placement**: {item -> quadrant description for each entry}
- **Comment**: {comment if present}
- **Field inputs**: {key = value for each entry in fields}
- **Option comments**: {option -> note for each entry in option_comments}
{if no VS responses}
No visual selection responses recorded.
---
## Artifacts
| Type | Title | Location |
| ---------- | ---------- | --------------------------------- |
| file | Design Doc | `docs/specs/2026-04-11-design.md` |
| git_commit | Phase 1 | `a1b2c3d` |
---
## Compliance Findings
{if findings exist}
| ID | Severity | Description | File |
| -------- | -------- | ---------------- | ---------------- |
| ISMS-001 | BLOCK | Hardcoded secret | src/config.ts:42 |
{if no findings}
No compliance issues found.
---
## Next Steps
{task_context summary of recommended next actions}
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 · 128 lines · 67 tokens per session scan A 12383b42e24c
bk-report is a skill published in the GitHub repository dandacompany/bluekiwi (23 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 892 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
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
reversa-sync
Convergência pós-coding do Reversa: destila a feature entregue num adendo em reversasdd/addenda/, mantendo a extração representativa entre re-extrações, sem tocar nos artefatos originais. Passo opcional do ciclo forward após /reversa-coding.
sred-project-organizer
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
slack-report-delivery
Deliver formatted network reports, audit results, topology diagrams, and compliance documentation to Slack channels with rich Block Kit formatting. Use when posting a health check report, sharing a security audit, delivering topology diagrams, or sending scheduled network reports to Slack.
notion
Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.
notion
Search, read, create, and update Notion pages and databases. Supports knowledge capture, meeting prep, research documentation, and spec-to-task workflows.