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 agentmods add skills/craftos-dev/craftbot/craftbot-skill-improvenpx skills add CraftOS-dev/CraftBot --skill craftbot-skill-improvegit clone --depth 1 https://github.com/CraftOS-dev/CraftBotWrote 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/craftos-dev/craftbot/craftbot-skill-improve)<a href="https://agentmods.dev/skills/craftos-dev/craftbot/craftbot-skill-improve"><img src="https://agentmods.dev/badge/skills/craftos-dev/craftbot/craftbot-skill-improve.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 | $0.00088 | $0.03304 |
| Opus 5 | $0.00044 | $0.01652 |
| Sonnet 5 | $0.00018 | $0.00661 |
| Haiku 4.5 | $0.00009 | $0.00330 |
Grade A, and why
craftbot-skill-improve 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 3d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CraftBot Skill Improver
Refine one existing skill using evidence from one task that used it. The handler that spawned this task already gathered everything you need into a single markdown file — read it, diff it against the live skill, apply small surgical edits, send the user a one-message summary of the changes, end the task. The handler has already posted "Improving skill <name>…" in chat for you, so do not duplicate that message. Your only chat message is the final presentation right before end_turn. Do not iterate with test cases. Do not run subagents.
What you receive
Your task instruction contains five lines (the two paths are absolute — pass them verbatim to read_file / stream_edit, do NOT prepend or modify any prefix):
Source file (read this — absolute path, use verbatim): <absolute path to SKILL_SOURCE_<id>.md>
Target file (edit this — absolute path, use verbatim): <absolute path to skills/<existing-name>/SKILL.md>
Mode: improve
Skill name: <existing-skill-name>
⚠️ Do not invent your own path for the target file. Using the literal value of
Target file:ensuresstream_editmodifies the actual installed SKILL.md.
SKILL_SOURCE_<task_id>.md has YAML frontmatter (mode: improve, target_skill, source_task_id, generated_at) and these body sections:
## Task name— the short task title shown in the action panel. A one-line summary of intent, not a verbatim instruction.## Outcome— status, created/ended timestamps, the skills the source task had attached, and any internalworkflow_id.## Action trace— every action and reasoning item, in order, withinput,output,error, and duration. This is your primary evidence — it is the durable record of what actually happened.## Existing SKILL.md— the verbatim contents ofskills/<target>/SKILL.mdas captured at the moment the workflow started.
The target skill exists. Your job is to edit it in place. The action trace is the evidence; the existing SKILL.md is what you are diffing against.
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.
- 3d ago First seen · 226 lines · 88 tokens per session scan A 63e2b06cf734
craftbot-skill-improve is a skill published in the GitHub repository CraftOS-dev/CraftBot (376 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 3,304 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
artifact-storage-policy
管理 Codex 交付物的專案識別、Google Drive／GitHub 路由、檔名、儲存位置與回讀驗證；凡工作報告、外部保存、交付成果或新 repository 選擇涉及遠端儲存時使用。.
output-contract
任務完成前需要一致交付格式、修改清單、測試結果、待確認事項、或使用者明確要求「完成後列出」時使用。適用於程式碼、設定、文件、skills、同步與多步驟任務收尾；本 Skill 不取代內容 readiness 或風險檢查。.
save-to-notion
將 Codex 對話、回答、決策、工作流程與可重用知識整理到使用者的 Notion 知識 Hub。當使用者明確說「save to notion」，或要求保存、歸檔、整理、分類、版本化、更新到 Notion 時使用；若只是要求產出一般報告或文件，除非另有指定，不要觸發 Notion 實際寫入。.
delivery-manifest
每次產生、修改、上傳或寄送檔案後，產生統一的交付物索引 (Delivery Manifest)，並嚴格控管 Google Drive 上傳路徑。.
intent-to-mission-blueprint
Convert human operational intent into a Tandem mission blueprint with phased workstreams, explicit handoffs, reusable outputs, and recurrence-aware setup.
marketing-brand-voice
Legacy fallback for brand governance and style policy work. Prefer copywriting and copy-editing for operational production tasks. Use when documenting or auditing voice rules, not as the default drafting workflow.