JetBrains/thinkrail is a desktop and mobile client that embeds the pi coding agent inside an interface for editing code and managing development workspaces. Developers use it to work on Git repositories through separate worktrees, a Monaco editor, terminals, Git views, specifications, and concurrent agent sessions. The catalogue entries are skills and instructions for its agent-based development workflow.
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 JetBrains/thinkrail --skill setting-up-a-projectgit clone --depth 1 https://github.com/JetBrains/thinkrailWrote 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/jetbrains/thinkrail/setting-up-a-project)<a href="https://agentmods.dev/skills/jetbrains/thinkrail/setting-up-a-project"><img src="https://agentmods.dev/badge/skills/jetbrains/thinkrail/setting-up-a-project/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/jetbrains/thinkrail/setting-up-a-project"><img src="https://agentmods.dev/badge/skills/jetbrains/thinkrail/setting-up-a-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00470 |
| Opus 5.5 | $0.00020 | $0.00188 |
| Sonnet 5.5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
setting-up-a-project 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 10d 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
Setting up a project — dispatcher
The single entry point for turning a project into a spec graph. Figure out which situation you're in, then follow the matching skill — don't improvise the flow yourself.
1. Detect
Look at the workspace and use the spec tools (spec_grep / spec_graph):
- Is there already a spec graph (a
goal-and-requirements.mdor anySPEC.md)? - Is there real source code, or is the repo empty / near-empty (just a README or scaffolding)?
2. Route
| Situation | Follow |
|---|---|
| Already has specs | Don't redo it. Briefly offer to review/extend the graph (fill obvious gaps — a missing architecture.md, un-specced modules). Other work routes as usual: features, behavior changes, and bug fixes through brainstorming; work that changes no behavior proceeds directly. Declined → stop. Accepted → Graph extension below. |
| No specs · empty / near-empty repo | The starting-a-new-project skill — interview the user to turn the idea into goal-and-requirements.md. |
| No specs · real source code | The importing-a-codebase skill — analyze the code + agent files and draft the first spec graph, asking only for intent the code can't reveal. |
Read and follow that skill's steps.
Graph extension (no dedicated skill)
No dedicated skill covers extending an existing graph. If the offer is accepted, align and adapt to the user's request with your own judgment, holding the writing-specs bar without a routing announcement.
Handoff
Ends by naming exactly one of: starting-a-new-project, importing-a-codebase, or — when specs already exist — the review/extend offer above (declined → stop; accepted → graph extension on judgment against the writing-specs bar).
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.
- 10d ago Changed da97c4d00847
- 1mo ago Changed · +1 lines · -27 tokens per session 1ddb78aa3db3
- 1mo ago First seen · 38 lines · 76 tokens per session scan A 057f0aae9417
setting-up-a-project is a skill published in the GitHub repository JetBrains/thinkrail (1,024 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 470 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
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
skillpack-creator
Create a reusable SkillPack from a successful completed task. Use when the user wants to convert a one-off research, coding, analysis, or content workflow into a distributable local SkillPack with skillpack.json, local skills under skills/, starter prompts, start scripts, and an optional zip package.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
bello-config-advisor
Inspect a coding task, repository, and user preferences, then recommend one concrete Bello configuration and decide whether a separate planning pass should precede execution. Use when the user asks to choose or optimize a Bello setup before a run, from Codex, Claude Code, or another host. Do not use merely to monitor…
vigilante-create-issue
Help a human author write an implementation-ready GitHub issue that Vigilante can execute reliably.
rn-device-control
This skill should be used when the user asks to "control the simulator", "take a screenshot", "boot the emulator", "install the app", "read UI hierarchy", "manage device state", "open a deep link", "grant permissions", "stream native logs", "disable animations", "change device locale", or needs guidance on xcrun…