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/mitodl/agent-kit/witan-workflownpx skills add mitodl/agent-kit --skill witan-workflowgit clone --depth 1 https://github.com/mitodl/agent-kitWhat 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.00089 | $0.01176 |
| Opus 5 | $0.00044 | $0.00588 |
| Sonnet 5 | $0.00018 | $0.00235 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
witan-workflow 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Session Manager
Interactive entry point for the workflow tracking system. Invoke with /witan-workflow
at the start of a session, or /witan-workflow end before stopping.
On invocation
Step 1 — Check args.
If the user passed list: call workflow_project_list() with no filters,
print a table of all projects (slug, title, phase, status, repo), and stop.
If the user passed end: go to the End session section below.
If the user passed new: skip to Create new project below.
Otherwise (no args or unrecognized): proceed to Step 2.
Step 2 — List active projects.
Call workflow_project_list() (no args — defaults to active projects in the
current repo). If the MCP call fails, tell the user the witan server
is not connected and stop.
Step 3 — Ask the user what to link to.
Build an AskUserQuestion with one question:
- Header: "Link session"
- Question: "Which project does this session belong to?"
- If there are 1–3 active projects: offer each as a labelled option
(label = title, description = "slug:
{slug}· phase: {phase}"), plus "Create new project" and (if >0 projects exist) "None / untracked". - If there are 0 active projects: offer "Create new project" and "None / untracked" only.
- If there are 4+ active projects: list them as text, ask the user to type a
slug or "new", then use
workflow_project_get(slug)to confirm the choice.
Step 4 — Handle the response.
If "None / untracked": do nothing, stop. The session won't be tracked.
If "Create new project": go to Create new project below, then continue to Step 5.
Otherwise: the user picked an existing project. Note its slug and phase.
Step 5 — Ask for the session phase.
Ask: "What phase is this session?" with options matching the project's valid
phases: discovery, spec, implementation, delivery. Pre-select the
project's current phase as the default (first option, labelled "(current)").
Step 6 — Start the session.
Call:
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 · 141 lines · 89 tokens per session scan A cc56f85bc6d7
witan-workflow is a skill published in the GitHub repository mitodl/agent-kit (2 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 89 tokens to every session and 1,176 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…