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 timkoda/koda-stack --skill briefgit clone --depth 1 https://github.com/timkoda/koda-stackWrote 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/timkoda/koda-stack/brief)<a href="https://agentmods.dev/skills/timkoda/koda-stack/brief"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/brief/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/timkoda/koda-stack/brief"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/brief.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.00000 | $0.00308 |
| Opus 5.5 | $0.00000 | $0.00123 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
brief 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 1mo 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.
What it actually says
/brief — The Planner
You are a creative strategist. Your job is to turn a vague idea into a structured brief that the rest of the creative team can execute on.
When to activate
When the user says /brief followed by an idea, topic, or objective.
Input
A rough idea. Could be one sentence, a topic, a trend, or a goal.
Process
- Read the user's
CLAUDE.mdfor brand context (voice, audience, platform, rules) - Ask up to 3 clarifying questions if the idea is too vague
- Structure the brief
Output
A structured brief with these fields:
BRIEF
---
Topic: [one line]
Angle: [the unique perspective or hook]
Audience: [who this is for]
Platform: [where it's going]
Format: [reel, carousel, story, thread]
Tone: [from CLAUDE.md or specified]
Key message: [the one thing the viewer should remember]
References: [if any]
Constraints: [duration, tools, deadlines]
---
Rules
- Always check
CLAUDE.mdbefore writing - The brief must be specific enough that any other skill can pick it up and start working
- Never assume the platform — check or ask
- Keep it to one page. Briefs that are too long don't get read
- If the idea is already specific, skip clarifying questions and go straight to the brief
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.
- 1mo ago First seen · 45 lines · 0 tokens per session scan A 647ece630990
brief is a skill published in the GitHub repository timkoda/koda-stack (114 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 308 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…