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 KaydenClark/LLM_Workbench --skill to-ticketsgit clone --depth 1 https://github.com/KaydenClark/LLM_WorkbenchWrote 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/kaydenclark/llm_workbench/to-tickets)<a href="https://agentmods.dev/skills/kaydenclark/llm_workbench/to-tickets"><img src="https://agentmods.dev/badge/skills/kaydenclark/llm_workbench/to-tickets/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/kaydenclark/llm_workbench/to-tickets"><img src="https://agentmods.dev/badge/skills/kaydenclark/llm_workbench/to-tickets.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.00018 | $0.00468 |
| Opus 5 | $0.00009 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
to-tickets 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 today.
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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Tickets
The assigned SPEC.md is the only ticket store. TASKBOARD.md is a generated
projection, not a second tracker.
For v3, confirm the assigned spec resolves through workbench/manifest.json
before changing it. Never recreate a root specs/ queue or a project-local
skill-discovery tree.
Process
- Read the assigned
SPEC.mdand the relevant source and tests. Do not select an unassigned spec. - Propose vertical slices that each deliver a checkable behavior in one context.
Apply the
/tracer-bulletdiscipline so each slice pierces every layer of the project's stack rather than one layer. Give each a short outcome-oriented title, real blockers, done criteria, and closing proof. Prefer an independent first tracer bullet; use expand-contract when a wide refactor cannot stay green by vertical slice. - Present the proposed table and ask for approval before changing durable work state. Confirm that slice size and blocking edges are right.
- After approval, use
spec-workbench.mjs next-id S-### --prefix TK --jsonfor each new label. It proposes a letter-bearing ID from the whole Workbench inventory without reserving it; save each planned row before requesting the next. Preserve existing spec-qualified numeric ticket references. Update only the assigned spec'sVertical Implementation Slicestable. Preserve completed rows and append-only evidence. Keep unresolved owner decisions visible as blockers. Create no parallel ticket or proof store. - Run
node workbench/tools/spec-workbench.mjs renderto refresh the generatedTASKBOARD.md, then runnode workbench/tools/spec-workbench.mjs doctor. Execution later uses the claim and close commands inRUNBOOK.mdone eligible ticket at a time.
Set the normal stance explicitly in each assigned TASK (ticket) and its SPEC during authorized decomposition. TASK is the existing ticket, not another file. An executing agent investigates within its assignment and never creates its own next task; these planning tools require owner-directed planning authority.
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.
- today Changed · -1 lines a76015ba5701
- yesterday Changed b7f02734d904
- 3d ago Changed · +11 lines 24e3bfc23c83
- 10d ago First seen · 29 lines · 18 tokens per session scan A 6939f20f89b4
to-tickets is a skill published in the GitHub repository KaydenClark/LLM_Workbench (2 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 468 once invoked, about $0.0001 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.