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/migrate-project)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/migrate-project"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/migrate-project/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/migrate-project"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/migrate-project.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.00019 | $0.01421 |
| Opus 5.5 | $0.00008 | $0.00568 |
| Sonnet 5.5 | $0.00004 | $0.00284 |
| Haiku 4.5 | $0.00002 | $0.00142 |
Grade A, and why
migrate-project 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate Project Prompt
Copy-Paste Template
Migrate my existing project at [PROJECT_PATH] to use the AI development framework.
Project details:
- Language/framework: [e.g., Python/Streamlit, Node.js/React]
- Has existing tests: [yes/no]
- Has Git repo: [yes/no]
- Current state: [working/partial/legacy]
I want a [minimal/full] migration:
- Minimal: Add AI resources (agents, instructions, skills, prompts) only
- Full: Add AI resources + documentation + IDE settings
After migration, analyze the codebase and suggest improvements.
Purpose
Complete guide for migrating an existing project to the AI Agentic Development Framework. Use this when you have a project you want to integrate with AI development resources.
When to Use
- You have an existing project without AI resources
- You want to add AI assistance to a legacy project
- You're onboarding a project into the framework
Quick Migration Commands
Minimal Migration (Add AI Resources Only)
# Navigate to your project scripts folder
cd <path-to-project-scripts>
# Migrate your project
.\migrate-project.ps1 -ProjectPath "<path-to-your-project>"
Full Migration (Add AI Resources + Docs + VS Code Settings)
cd <path-to-project-scripts>
.\migrate-project.ps1 -ProjectPath "<path-to-your-project>" -Full
What Gets Added
Minimal Migration
| Resource | Count | Purpose |
|---|---|---|
agents/ |
18 | AI personas for different tasks |
instructions/ |
13 | Coding guidelines by file type |
skills/ |
9 | Reusable AI capabilities |
prompts/ |
9 | Common prompt templates |
sync-ai-resources.ps1 |
1 | Update script |
Full Migration (Additional)
| Resource | Purpose |
|---|---|
.vscode/settings.json |
VS Code configuration |
docs/developer-handbook.md |
AI resource usage guide |
docs/user-guide.md |
Project lifecycle guide |
Migration Workflow
Phase 1: Pre-Migration Assessment
Before migrating, understand your project:
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 · 210 lines · 19 tokens per session scan A 24b7716e4205
migrate-project is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,421 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
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
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.
observe
Show the observability web UI URL (it autostarts with the session); stop or restart it.
accept
Command dispatcher for accept.
change
Command dispatcher for change.
checklist
Generate a custom checklist for the current feature based on user requirements.