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/jenreh/appkit/boostnpx skills add jenreh/appkit --skill boostgit clone --depth 1 https://github.com/jenreh/appkitWhat 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.00138 | $0.01078 |
| Opus 5 | $0.00069 | $0.00539 |
| Sonnet 5 | $0.00028 | $0.00216 |
| Haiku 4.5 | $0.00014 | $0.00108 |
Grade A, and why
boost 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boost — Prompt Refinement Workflow
Help the user turn a rough idea or vague request into a precise, detailed implementation plan prompt. Do NOT write or generate any implementation code. Your output is always a refined prompt — not the solution itself.
Workflow
0. Enter plan mode
Call EnterPlanMode immediately. This enforces the no-code constraint at the tool level and ensures the final refined prompt is delivered through the plan approval interface.
1. Understand the raw request
Read what the user gave you. If it's a vague idea ("I want to add auth"), that's fine — start there. If it's a half-written prompt, work from it.
Ask yourself:
- What is the user actually trying to build or change?
- What's still unclear or underspecified?
2. Explore the project
Use available tools to build context before asking the user anything:
- Memory MCP (
memory/*, if available): query first — the user may have prior decisions, preferences, or architectural notes stored from past sessions that directly inform this task. Search for relevant entities (project name, framework, patterns, past decisions on similar features). - Read key files:
CLAUDE.md,README.md, entry points, relevant modules touched by the task - Bash/Glob/Grep: find related code, existing patterns, current architecture
- Reasoning MCP (
code-reasoning/*, if available): use extended thinking when the task involves non-obvious trade-offs, complex dependency chains, or ambiguous scope — e.g. "should this live in the service layer or the router?", "what migration strategy fits this schema?". Don't use it for simple lookups. - WebSearch: look up relevant library APIs, best practices, recent changes if the task involves third-party tooling
- context7 / upstash MCP (if available): fetch up-to-date framework docs for any libraries involved (e.g. Reflex, FastAPI, SQLModel, Mantine)
Don't ask the user things you can find yourself. Memory and reasoning give you two advantages: memory surfaces what the user already decided so you don't ask again; reasoning helps you resolve ambiguity without guessing.
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 · 86 lines · 138 tokens per session scan A ddc783e9f085
boost is a skill published in the GitHub repository jenreh/appkit (4 stars, last pushed 6d ago), licensed MIT. It adds 138 tokens to every session and 1,078 once invoked, about $0.0007 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-31.
Other skills, from other repositories
ima2
Use the ima2-gen CLI/server to generate, edit, inspect, and manage local AI image generation jobs.
videoagent-image-studio
Tired of juggling 8 API keys? This skill gives you one-command access to Midjourney, Flux, Ideogram, and more, with zero setup. Use when you want to generate any image without worrying about API keys.
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
image
Use this Skill when a game plan needs a single-subject concept image, a character reference cleaned for image-to-3D, or a front-facing transparent T-pose image for downstream character reconstruction. T-pose generation is an image-generation and image-editing task; it is not a separate asset category.
comfyui-skill-openclaw
Run registered ComfyUI workflows through the fast comfyui-skill CLI, and use the official local Comfy MCP for live template, node, model, validation, and orchestration capabilities. Use this Skill when: (1) The user requests to "generate an image", "draw a picture", or "execute a ComfyUI workflow". (2) The user has…
audio
Use this Skill when a game plan requires dialogue, voice lines, sound effects, foley, ambience, or other offline WAV assets. This is asset generation, not a runtime audio-playback contract; use the selected engine context after an asset has passed review.