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.
git clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/project-setup)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/project-setup"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/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/saajunaid/caddis-plugin/project-setup"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/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.00018 | $0.01629 |
| Opus 5.5 | $0.00007 | $0.00652 |
| Sonnet 5.5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
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 — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Setup Prompt
Copy-Paste Template
Set up a new project for me:
- Project name: [my-project-name]
- Language/framework: [e.g., Python/Streamlit, Python/FastAPI, Node.js/React]
- Database: [e.g., SQL Server, PostgreSQL, SQLite, none]
- Description: [Brief description of what the project will do]
- Location: [parent folder path where project should be created]
Please:
1. Create the project structure
2. Set up a virtual environment
3. Install base dependencies
4. Add AI resources (agents, instructions, skills)
5. Create starter config files (.env.example, .gitignore)
6. Initialize Git repository
Purpose
Complete guide for setting up a new project from start to finish. Use this prompt to get step-by-step instructions for creating a properly configured project.
When to Use
- Starting a brand new project
- Setting up your development environment for the first time
- Onboarding to the development framework
- Need a quick reference for setup commands
Quick Setup Commands
Create a New Project
# Navigate to your project folder (replace with your actual path)
cd <path-to-project>
# Create the project (replace 'my-project' with your project name and path)
.\new-project.ps1 -Name "my-project" -Path "<parent-folder-for-projects>"
# Open in your editor (e.g. VS Code, Cursor)
cd <parent-folder-for-projects>\my-project
code . # or: cursor . (depending on your IDE)
Set Up Development Environment
# Create virtual environment
python -m venv .venv
# Activate (Windows PowerShell)
.\.venv\Scripts\Activate.ps1
# Install dependencies
pip install -r requirements.txt
# Create environment config
Copy-Item .env.example .env
# Edit .env with your values
Verify Setup
# Check AI resources are synced
Get-ChildItem agents -Name
# Check Python environment
python --version
pip list
# Run the app
streamlit run src\app.py
Complete Setup Walkthrough
Phase 1: One-Time Setup (Per Developer Machine)
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 · 290 lines · 18 tokens per session scan A 882ac1d6fe5d
project-setup is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,629 once invoked, about $0.0001 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-09-09.
Other commands, from other repositories
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
prototype
Command dispatcher for prototype.
specify
Command dispatcher for specify.
run-workflow
Validate and establish the proven rn-dev-agent operating sequence before a real React Native journey — declared package manager and dependencies, read-only inventory, typed session recovery, one exclusive device, managed integration and Metro, only the requested proof, reverse-order cleanup.
status
Show the current in-flight task state — active phase, plan, gate, sign-off progress, and next action. Read-only; writes nothing.