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/kaydenclark/llm_workbench/genesisnpx skills add KaydenClark/LLM_Workbench --skill genesisgit 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/genesis)<a href="https://agentmods.dev/skills/kaydenclark/llm_workbench/genesis"><img src="https://agentmods.dev/badge/skills/kaydenclark/llm_workbench/genesis.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.1 | $0.00026 | $0.00367 |
| Opus 5 | $0.00013 | $0.00183 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
genesis 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 5d 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
Use Genesis only for a new greenfield project. If the target already contains
real code, history, or project controls, route to /adoption instead.
- Locate the canonical Workbench source named by the workspace controls and
read
templates/GENESIS.mdcompletely. Treat it as the bootstrap procedure; this skill is only its conversational entrypoint. - Preserve the founding prompt verbatim, verify the target path is inside the authorized workspace, and ask only when a missing answer changes architecture, privacy, money, credentials, or destructive risk.
- Run the Genesis phases in order. Create filled controls, one stable spec, the smallest runnable vertical proof, and exact Runbook commands. Do not leave a second planning or proof store.
- Establish Git recovery immediately. When the current authorization and authenticated repository namespace permit remote creation, create a private remote if none was supplied. Never infer public visibility, change credentials, or overwrite an existing remote.
- Follow the workspace branch policy. By default, publish task checkpoints and
completed work to a task branch, promote verified work only to
integration, and leaveintegrationtomainfor the owner. - Always commit and push after every completed ticket and before yielding incomplete work. A local-only scaffold is not a completed Genesis handoff.
- Run the generated project's targeted and full verification, update the owning spec evidence, render its Taskboard, run doctor, and report the remote recovery ref plus the under-one-minute demo.
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.
- 5d ago First seen · 31 lines · 26 tokens per session scan A 2c89e004624e
genesis is a skill published in the GitHub repository KaydenClark/LLM_Workbench (2 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 367 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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-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…