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/craigjmidwinter/katra/embednpx skills add craigjmidwinter/katra --skill embedgit clone --depth 1 https://github.com/craigjmidwinter/katraWhat 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.00088 | $0.02336 |
| Opus 5 | $0.00044 | $0.01168 |
| Sonnet 5 | $0.00018 | $0.00467 |
| Haiku 4.5 | $0.00009 | $0.00234 |
Grade A, and why
katra 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
katra
Keep a living dev log while you work, using the katra CLI (or the
katra-mcp MCP tools, if connected). The log is markdown entries with embedded
rich components, served as a live page and committed alongside the code.
The harness-neutral workflow is the public contract: https://craigjmidwinter.github.io/katra/workflow. This skill is a Claude Code delivery mechanism for the same task/epic/spec/entry/decision/stamp loop; it does not define behavior unavailable to a plain CLI or another coding harness.
The model (read this first)
- A katra lives in
katra/at the repo root:entries/(one markdown file per post) +media/+config.yml. Runkatra listto see if one exists; if not,katra init. - A draft is an entry with no commit hash. It renders in the "In Progress" panel immediately — there is no scratch file and no promote step. The draft is the running post; you stamp it at commit time (hash + diffstat) and it drops into the log. Nothing can get stuck.
Specs come before drafts
Before starting a task, check whether it is specced
(katra task list --status specced). That means a design is already
committed — its spec: frontmatter is a node slug in the katra, or a path
relative to the repo root. Read that file before writing any code; it exists
so you do not have to re-derive intent from a conversation that will not be
there next session.
If you are the one writing the design, not just building from one already committed, and the task deserves it: write it (a decision, an article, or any other markdown), then attach it —
katra task spec <task-slug> <ref>
— and commit the artifact plus task pointer as one planning change. This moves
the task todo/empty → specced and leaves a further-along status alone. Then
katra task start <task-slug> and implement from the committed spec.
Keep logging entries as you go, the same as any other work — and let them say
where the build diverged from the plan and why. That comparison is what makes
the entry worth more than the spec alone.
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 · 190 lines · 88 tokens per session scan A 73a59f8d2be8
katra is a skill published in the GitHub repository craigjmidwinter/katra (0 stars, last pushed 6d ago), licensed MIT. It adds 88 tokens to every session and 2,336 once invoked, about $0.0004 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
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…