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 agentmods add commands/adilkalam/orca/project-setupgit clone --depth 1 https://github.com/adilkalam/orcaWhat 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 | $0.00011 | $0.02834 |
| Opus 5 | $0.00005 | $0.01417 |
| Sonnet 5 | $0.00002 | $0.00567 |
| Haiku 4.5 | $0.00001 | $0.00283 |
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 yesterday.
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 — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/project-setup - Project Conventions Wizard
Guide users through project structure decisions and generate a CLAUDE.md file tailored to their project type. Command: $ARGUMENTS
You are a project setup orchestrator that:
- Detects project type automatically
- Observes existing project patterns
- Asks focused questions (4 total: 2 shared + 2 type-specific)
- Generates actionable CLAUDE.md rules
1. Determine Subcommand
Parse $ARGUMENTS to determine mode:
| Subcommand | Behavior |
|---|---|
init or empty |
Full initialization flow |
update |
Update existing CLAUDE.md with new conventions |
audit |
Check CLAUDE.md health and staleness |
2. Detect Project Type
Run project type detection (inspect package.json / requirements.txt / pyproject.toml / go.mod / Gemfile / Cargo.toml and framework markers):
# iOS/Swift
if ls *.xcodeproj >/dev/null 2>&1 || ls *.xcworkspace >/dev/null 2>&1; then
PROJECT_TYPE="ios"
# Next.js
elif [ -f "package.json" ] && grep -q '"next"' package.json 2>/dev/null; then
PROJECT_TYPE="nextjs"
# React
elif [ -f "package.json" ] && grep -q '"react"' package.json 2>/dev/null; then
PROJECT_TYPE="react"
# Python
elif [ -f "requirements.txt" ] || [ -f "pyproject.toml" ]; then
PROJECT_TYPE="python"
# Flutter
elif [ -f "pubspec.yaml" ]; then
PROJECT_TYPE="flutter"
# React Native
elif [ -f "package.json" ] && [ -d "ios" ] && [ -d "android" ]; then
PROJECT_TYPE="react-native"
# Generic
else
PROJECT_TYPE="generic"
fi
Output: "Detected project type: {PROJECT_TYPE}"
3. Observe Project Structure (Always On)
BEFORE asking questions, scan for existing patterns:
# Archive-like folders
find . -maxdepth 2 -type d \( -name ".archived" -o -name "_deprecated" -o -name "old" -o -name "archive" \) 2>/dev/null | head -5
# Working/temp folders
find . -maxdepth 2 -type d \( -name ".claude" -o -name ".tmp" -o -name "temp" -o -name "scratch" \) 2>/dev/null | head -5
# Documentation folders
find . -maxdepth 2 -type d \( -name "docs" -o -name "documentation" -o -name "wiki" \) 2>/dev/null | head -5
# Check for existing CLAUDE.md
ls -la CLAUDE.md 2>/dev/null
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.
- yesterday First seen · 480 lines · 11 tokens per session scan A 044b73457c19
project-setup is a command published in the GitHub repository adilkalam/orca (2 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,834 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.