Borrowing it
Nothing to install: this file belongs to llcoolblaze/claude-boris. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/llcoolblaze/claude-boris/main/.claude/skills/boris-workflow/SKILL.mdgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/llcoolblaze/claude-boris/boris-workflow)<a href="https://agentmods.dev/skills/llcoolblaze/claude-boris/boris-workflow"><img src="https://agentmods.dev/badge/skills/llcoolblaze/claude-boris/boris-workflow/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/llcoolblaze/claude-boris/boris-workflow"><img src="https://agentmods.dev/badge/skills/llcoolblaze/claude-boris/boris-workflow.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.00038 | $0.01061 |
| Opus 5.5 | $0.00015 | $0.00424 |
| Sonnet 5.5 | $0.00008 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
boris-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 2mo 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boris Workflow Methodology
This skill documents the workflow used by Boris Cherny, creator of Claude Code. Use these principles when orchestrating development tasks.
Core Principles
1. Plan First, Execute Second
"Most sessions start in Plan mode. Go back and forth until I like the plan. From there, auto-accept and Claude can usually 1-shot it."
Implementation:
- Always create a written plan before coding
- Get explicit approval before proceeding
- Plans should include: goal, steps, verification strategy
- A good plan enables 1-shot execution
2. Verification is Everything
"Give Claude a way to verify its work. If Claude has that feedback loop, it will 2-3x the quality."
Implementation:
- Every change must pass automated checks
- Tests, types, lint, build - all must pass
- Manual verification for UI changes
- Never skip verification to save time
3. Living Documentation
"Anytime we see Claude do something incorrectly we add it to CLAUDE.md, so Claude knows not to do it next time."
Implementation:
- Update CLAUDE.md after every mistake
- Document patterns that work well
- Keep commands and processes current
- This compounds over time
4. Delegate to Specialists
"I use subagents regularly: code-simplifier, verify-app, and so on."
Implementation:
- Use Task tool to invoke specialist agents
- Match agent to task type
- Don't do everything yourself
- Specialists have focused expertise
5. Automate the Inner Loop
"I use slash commands for every workflow I do many times a day."
Implementation:
- Create commands for repeated workflows
- Commands should be self-contained
- Pre-compute context with inline bash
- Check commands into git for team sharing
The Boris Orchestration Pattern
When handling a task as the Boris orchestrator:
1. UNDERSTAND
- Parse the user's request
- Identify implicit requirements
- Assess scope and complexity
2. PLAN
- Create detailed execution plan
- Identify which agents to use
- Define verification criteria
- Present plan for approval
3. EXECUTE
- Delegate to appropriate agents
- Maintain coordination
- Handle failures gracefully
- Track progress
4. VERIFY
- Run all automated checks
- Invoke verify-app agent
- Use code-simplifier to clean up
- Iterate until all checks pass
5. SHIP
- Commit with good message
- Create PR with context
- Update CLAUDE.md if learned something
- Report completion
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.
- 2mo ago First seen · 164 lines · 38 tokens per session scan A 334f4263cf95
boris-workflow is a skill published in the GitHub repository llcoolblaze/claude-boris (49 stars, last pushed 9mo ago), licensed MIT. It adds 38 tokens to every session and 1,061 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…