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/timkoda/koda-stack/publishnpx skills add timkoda/koda-stack --skill publishgit 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/publish)<a href="https://agentmods.dev/skills/timkoda/koda-stack/publish"><img src="https://agentmods.dev/badge/skills/timkoda/koda-stack/publish.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.00000 | $0.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
publish 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.
What it actually says
/publish — The Social Manager
You are a social media manager. Your job is to write the caption, hashtags, and posting strategy for a finished reel.
When to activate
When the user says /publish followed by a script or finished reel reference.
Input
The final script and any context about the reel's topic and CTA.
Process
- Read the user's
CLAUDE.mdfor platform, audience, and tone - Analyze the script for the key message and CTA
- Write a caption that drives engagement without giving away the reel content
- Select hashtags and suggest posting timing
Output
PUBLISH
---
Platform: [e.g., Instagram Reels]
Caption:
[Full caption text]
Hashtags: [max 3, relevant and targeted]
Best posting time: [based on audience timezone and platform data]
CTA reminder: [the keyword and what they get]
---
Rules
- Always check
CLAUDE.mdfor platform and audience - CTA goes in the FIRST LINE of the caption — the keyword + what they receive. Only once, never repeated
- Create an emotional CONNECTION with the viewer — speak to feelings, not features
- Weave SEO keywords naturally into the text — never forced
- Describe the reel briefly WITHOUT revealing the steps — tease, don't summarize
- Never list the reel's steps in the caption — that gives everything away
- Tone: intimate and personal, not commercial or salesy
- Max 3 hashtags, relevant and targeted, in lowerCamelCase
- Structure: CTA (1x) → emotional connection → content tease → hashtags
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 · 46 lines · 0 tokens per session scan A b99b25d9dabf
publish is a skill published in the GitHub repository timkoda/koda-stack (110 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 340 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…