Borrowing it
Nothing to install: this file belongs to bringfire/rook-release. 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/bringfire/rook-release/main/.claude/skills/project-setup/SKILL.mdgit clone --depth 1 https://github.com/bringfire/rook-releaseWrote 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/bringfire/rook-release/project-setup)<a href="https://agentmods.dev/skills/bringfire/rook-release/project-setup"><img src="https://agentmods.dev/badge/skills/bringfire/rook-release/project-setup/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/bringfire/rook-release/project-setup"><img src="https://agentmods.dev/badge/skills/bringfire/rook-release/project-setup.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.00099 | $0.01072 |
| Opus 5.5 | $0.00040 | $0.00429 |
| Sonnet 5.5 | $0.00020 | $0.00214 |
| Haiku 4.5 | $0.00010 | $0.00107 |
Grade A, and why
project-setup 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 1mo 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup
Bootstrap the current project directory so Claude Code has Rook context when working here. Two actions:
- CLAUDE.md — Create or merge Rook agent instructions
- /init — Initialize Claude Code project configuration
Prerequisites
- Rook must be installed (MCP server registered in
~/.claude.json) - The current working directory should be the user's project folder,
NOT the Rook install directory (
%LOCALAPPDATA%\Rook)
Workflow
Step 0: Detect State
Check the current directory:
-
What is the current working directory? If it's the Rook install root (
%LOCALAPPDATA%\Rookor the Rook source repo), warn the user: "You're already in the Rook directory — this skill is for setting up your own project folders. cd to your project first." -
Does
./CLAUDE.mdexist?- No → Step 1A (create from template)
- Yes → check if it already contains Rook instructions (search
for the marker
<!-- rook-begin -->)- Marker found → tell user "Rook instructions already present in CLAUDE.md" and skip to Step 2
- No marker → Step 1B (merge into existing)
Step 1A: Create CLAUDE.md (no existing file)
Read the Rook agent instruction template. The canonical source is the
installed copy at %LOCALAPPDATA%\Rook\CLAUDE.md. If that doesn't
exist, use the template from the Rook repo at installer/CLAUDE.md.
Write a new ./CLAUDE.md with this structure:
<!-- rook-begin -->
{contents of the Rook CLAUDE.md template}
<!-- rook-end -->
Tell the user: "Created CLAUDE.md with Rook agent instructions. You can add your own project-specific notes above or below the Rook section."
Step 1B: Merge into existing CLAUDE.md
The user already has a CLAUDE.md with their own content. Append the Rook section at the end:
{existing CLAUDE.md content unchanged}
<!-- rook-begin -->
{contents of the Rook CLAUDE.md template}
<!-- rook-end -->
Rules:
- NEVER modify the user's existing content
- Always append at the end, never prepend
- Use the
<!-- rook-begin -->/<!-- rook-end -->markers so future updates can find and replace just the Rook section
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.
- 1mo ago First seen · 127 lines · 99 tokens per session scan A be05849a2b00
project-setup is a skill published in the GitHub repository bringfire/rook-release (6 stars, last pushed yesterday), licensed MIT. It adds 99 tokens to every session and 1,072 once invoked, about $0.0004 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-31.
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…
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…