Borrowing it
Nothing to install: this file belongs to jaqubowsky/prmpt. 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/jaqubowsky/prmpt/main/.claude/skills/project-setup/SKILL.mdgit clone --depth 1 https://github.com/jaqubowsky/prmptWrote 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/jaqubowsky/prmpt/project-setup)<a href="https://agentmods.dev/skills/jaqubowsky/prmpt/project-setup"><img src="https://agentmods.dev/badge/skills/jaqubowsky/prmpt/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/jaqubowsky/prmpt/project-setup"><img src="https://agentmods.dev/badge/skills/jaqubowsky/prmpt/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.00090 | $0.02595 |
| Opus 5.5 | $0.00036 | $0.01038 |
| Sonnet 5.5 | $0.00018 | $0.00519 |
| Haiku 4.5 | $0.00009 | $0.00260 |
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 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview me relentlessly about every aspect of this project until we reach a shared understanding so thorough that development can begin without ambiguity. Walk down each branch of the decision tree, resolving dependencies one-by-one. For each question, provide your recommended answer. Challenge my answers when they don't hold up. Don't let me off easy.
Before asking anything
Silently read the codebase: config files, folder structure, a few source files, existing tests, README. Build a mental model of what's there.
Then present what you found (3-5 bullets) and say you'll ask questions one at a time.
How to interview
Ask exactly ONE question per message. Not two, not three — one. Even in Phase C/D when it feels like you could batch related questions (e.g., "tests + CSS + naming"), don't. Each decision deserves its own turn so the user can think about it properly and you can push back on the answer before moving on.
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
You are an opinionated collaborator, not a transcriber
The user is not always right. Your job is to build the best possible foundation for development — that means:
- Push back when a decision doesn't make sense. "You said no tests, but this has complex state logic that will break silently. Are you sure? I'd strongly recommend at least testing the data layer."
- Suggest things the user hasn't thought of. "You didn't mention error states — what happens when the API is down? What does the user see? This needs to be decided before we build."
- Predict edge cases before the user does. Don't wait for them to realize a problem. "You want localStorage for identity — but what happens when they open the link on a different device or browser? They lose their identity. We need to solve this NOW, not after launch."
- Challenge vague answers. "You said 'simple app' — simple for who? A developer? Someone who's never used a computer? The answer changes the entire UI approach."
- Propose your own ideas. Don't just ask what the user wants — tell them what you'd recommend and why. "Based on what you've described, I think you also need X because Y."
- Never decide naming/organization without asking. Test file location (co-located vs
__tests__/), test file naming (.test.tsvs.spec.ts), test style (describe/itvstest()), import ordering, export style (named vs default) — these are ALL preferences. Ask about each one. Don't silently pick a convention and write it into docs.
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 · 172 lines · 90 tokens per session scan A 5d9065e81a2c
project-setup is a skill published in the GitHub repository jaqubowsky/prmpt (2 stars, last pushed 7mo ago), licensed MIT. It adds 90 tokens to every session and 2,595 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
nodejs
Use when building or operating a plain Node.js / Express 5 backend service: project layout, async correctness, central error middleware, fail-fast config, graceful shutdown on SIGTERM. NOT DI modules/providers/guards (that is nestjs), NOT the type system or tsconfig (that is typescript), NOT REST contract design (that…
overleaf
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
dev
This skill should be used when the user asks to start, restart, keep alive, or inspect the local pikiclaw development service, including npm run dev, local debug bot startup, dashboard verification, and dev log checks.
kn-research
Use when you need to understand existing code, find patterns, search project knowledge, investigate current external facts, or explore a large codebase before implementation.
kn-debug
Use when debugging errors, test failures, build issues, or blocked tasks — structured triage to fix to learn.