Borrowing it
Nothing to install: this file belongs to princeton-ddss/blackfish. 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/princeton-ddss/blackfish/main/.claude/commands/project-setup.mdgit clone --depth 1 https://github.com/princeton-ddss/blackfishWrote 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/commands/princeton-ddss/blackfish/project-setup)<a href="https://agentmods.dev/commands/princeton-ddss/blackfish/project-setup"><img src="https://agentmods.dev/badge/commands/princeton-ddss/blackfish/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/commands/princeton-ddss/blackfish/project-setup"><img src="https://agentmods.dev/badge/commands/princeton-ddss/blackfish/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.00000 | $0.00582 |
| Opus 5.5 | $0.00000 | $0.00233 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up GitHub Project integration for Claude Code workflow tracking.
$ARGUMENTS: [owner] [project-number]
Step 1: Get project details
If arguments not provided, ask the user:
- Owner: organization name (e.g., "princeton-ddss") or "@me" for personal projects
- Project number: the project number (visible in project URL)
Step 2: Query project structure via GraphQL
For organization projects:
gh api graphql -f query='
query($owner: String!, $number: Int!) {
organization(login: $owner) {
projectV2(number: $number) {
id
title
field(name: "Status") {
... on ProjectV2SingleSelectField {
id
options {
id
name
}
}
}
}
}
}
' -F owner="<owner>" -F number=<number>
For personal projects (when owner is "@me"), use this query instead:
gh api graphql -f query='
query($number: Int!) {
viewer {
projectV2(number: $number) {
id
title
field(name: "Status") {
... on ProjectV2SingleSelectField {
id
options {
id
name
}
}
}
}
}
}
' -F number=<number>
Step 3: Validate required status options
The project MUST have these status options (names can vary slightly):
- Backlog (or "Todo", "New")
- Ready (or "Ready to Start")
- In Progress (or "Active", "Working")
- In Review (or "Review", "Pending Review")
- Done (or "Closed", "Complete")
If any are missing, warn the user and ask if they want to proceed anyway.
Step 4: Write configuration file
The config file .claude/projects.json is an array of projects. If the file exists, append to it (avoiding duplicates by project_id). If not, create a new array.
Each project entry:
{
"name": "<title-from-query>",
"owner": "<owner>",
"project_number": <number>,
"project_id": "<project-id-from-query>",
"fields": {
"status": {
"id": "<field-id-from-query>",
"options": {
"<option-name>": "<option-id>",
...
}
}
}
}
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 · 100 lines · 0 tokens per session scan A e103870abe40
project-setup is a command published in the GitHub repository princeton-ddss/blackfish (26 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 582 tokens. 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-09-01.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
land
Resolve and squash merge one named, currently authorized pull request.
standup
Review my git commits from the past workday and generate a standup summary.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
weekly-summary
Generate weekly work summary from git activity.
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.