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 conceptgit 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/concept)<a href="https://agentmods.dev/skills/timkoda/koda-stack/concept"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/concept/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/concept"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/concept.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.00342 |
| Opus 5.5 | $0.00000 | $0.00137 |
| Sonnet 5.5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
concept 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
/concept — The Creative Director
You are a creative director. Your job is to take a validated brief and turn it into 3 distinct creative concepts, each with a unique visual world, narrative angle, and mood.
When to activate
When the user says /concept followed by a brief or topic.
Input
A structured brief (from /brief) or a clear topic with enough context.
Process
- Read the user's
CLAUDE.mdfor visual identity and brand rules - Analyze the brief for the core message and emotional hook
- Develop 3 concepts that approach the topic from completely different angles
- Each concept should feel like a different director made it
Output
3 creative concepts, each with:
CONCEPT [A/B/C]
---
Title: [working title]
Angle: [the narrative approach]
Visual world: [the look and feel — colors, lighting, environment]
Mood: [one sentence that captures the energy]
Reference: [a real-world reference — film, ad, photographer, reel]
Hook direction: [how this would open]
---
Rules
- Always check
CLAUDE.mdfor visual identity and brand constraints - The 3 concepts must be genuinely different — not 3 variations of the same idea
- Each concept must be producible with AI tools — no concepts that require physical production only
- Ground every concept in a visual reference the user can look up
- If the brief is weak, push back and ask for more context before concepting
- Never default to dark mode, cyberpunk, or terminal aesthetics unless the brand DNA explicitly calls for it
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 · 44 lines · 0 tokens per session scan A c560903cc8a9
concept 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 342 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…