project-setup

project-setup is a command for Claude Code from princeton-ddss/blackfish. It costs 0 tokens per session (582 once invoked), scanned A, original, MIT.

Set up GitHub Project integration for Claude Code workflow tracking.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/princeton-ddss/blackfish/project-setup
Clone the repo
git clone --depth 1 https://github.com/princeton-ddss/blackfish

Made for: Claude Code.

Wrote 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.

agentmods badge for project-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/princeton-ddss/blackfish/project-setup.svg)](https://agentmods.dev/commands/princeton-ddss/blackfish/project-setup)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 582 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00582
Opus 5 $0.00000 $0.00291
Sonnet 5 $0.00000 $0.00116
Haiku 4.5 $0.00000 $0.00058

Measured 2d ago against content hash e103870abe40, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/commands/project-setup.md · 100 lines

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>",
        ...
      }
    }
  }
}

Read the full file on GitHub · 100 lines

Changes

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.

  1. 2d ago First seen · 100 lines · 0 tokens per session scan A e103870abe40

Subscribe to this mod's changes

project-setup is a command published in the GitHub repository princeton-ddss/blackfish (24 stars, last pushed 5d 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.