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/file-formatnpx skills add CraftOS-dev/CraftBot --skill file-formatgit clone --depth 1 https://github.com/CraftOS-dev/CraftBotWhat 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.00125 | $0.01470 |
| Opus 5 | $0.00063 | $0.00735 |
| Sonnet 5 | $0.00025 | $0.00294 |
| Haiku 4.5 | $0.00013 | $0.00147 |
Grade A, and why
file-format 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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Format Standards
Overview
This skill provides consistent formatting and design standards across all file outputs. It ensures consistent branding, typography, layout, and structure across every file type and document purpose the agent generates.
Standards live in resources/FORMAT.md, organized into three layers that the agent reads on demand.
How to Read FORMAT.md
resources/FORMAT.md is divided into sections using ## section-name headings. Each section is separated by a --- horizontal rule divider.
To extract the formatting rules you need:
- Use grep to search
resources/FORMAT.mdfor the section keyword (e.g.,"## pptx","## finance-report") - Read from the matched
## headingdown to the next---divider — that is the complete section - Each section is self-contained: everything between
## headingand the next---belongs to that section
Section types in FORMAT.md:
## global— universal standards (always at the top)## <file-type>— file-format-specific rules (e.g.,## pptx,## docx,## xlsx,## pdf,## md,## html)## <purpose>— document-purpose-specific rules (e.g.,## finance-report,## seo-audit,## meeting-minutes)
Users can add their own file-type or purpose sections at any time. Do not assume the list is fixed — always search for a match.
3-Layer Lookup Process
Before generating any file, perform these lookups IN ORDER:
Layer 1: Global Standards (ALWAYS read)
Search for ## global in resources/FORMAT.md. Read the entire section.
This section defines universal rules: brand color palette, typography scale, writing conventions, and general layout. These apply to every file you generate.
Layer 2: File-Type Standards (ALWAYS read)
Search resources/FORMAT.md for the ## <file-type> section matching your output format. The section name matches the file extension or format name.
Examples:
- Generating a
.pptxfile → search for## pptx - Generating a
.docxfile → search for## docx - Generating a
.pdffile → search for## pdf
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.
- 2d ago First seen · 130 lines · 125 tokens per session scan A f3b638b53cff
file-format is a skill published in the GitHub repository CraftOS-dev/CraftBot (376 stars, last pushed 2d ago), licensed MIT. It adds 125 tokens to every session and 1,470 once invoked, about $0.0006 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
turix-mac
Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.
browser-control
Control web pages in an existing Chromium remote-debugging session with deterministic sagui commands or the browser-only AI Agent. Use when Claude Code needs to inspect tabs, observe semantic elements, navigate, click, type, send keys, scroll, or complete a browser goal through CDP without controlling native macOS UI…
agent-smoke-test
Run manual development checks for SwiftAutoGUI AI Agent actions through the local sagui CLI. Use when Claude or Codex needs to test app-control or Accessibility BasicAction generation on macOS.
macos-control
Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.
open-record-replay
Record a user-demonstrated macOS workflow with the Open Record/Replay CLI, inspect the captured event stream, prepare a skill evidence package, and hand it to the host agent's native skill creator. Use when the user asks the agent to watch them perform a task, record a workflow, or create/refine a reusable Computer…
artifact-storage-policy
管理 Codex 交付物的專案識別、Google Drive／GitHub 路由、檔名、儲存位置與回讀驗證；凡工作報告、外部保存、交付成果或新 repository 選擇涉及遠端儲存時使用。.