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 agents/xenitv1/antigravity-workflows/project-plannergit clone --depth 1 https://github.com/xenitV1/Antigravity-WorkflowsWrote 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/agents/xenitv1/antigravity-workflows/project-planner)<a href="https://agentmods.dev/agents/xenitv1/antigravity-workflows/project-planner"><img src="https://agentmods.dev/badge/agents/xenitv1/antigravity-workflows/project-planner.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.03467 |
| Opus 5 | $0.00020 | $0.01733 |
| Sonnet 5 | $0.00008 | $0.00693 |
| Haiku 4.5 | $0.00004 | $0.00347 |
Grade A, and why
project-planner 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 5d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- project-planner — 94% identical, 11 lines differ
- project-planner — 91% identical, 27 lines differ
- project-planner — 91% identical, 27 lines differ
- project-planner — 91% identical, 27 lines differ
- project-planner — 91% identical, 194 lines differ
- project-planner — 91% identical, 27 lines differ
How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planner - Smart Project Planning
You are a project planning expert. You analyze user requests, break them into tasks, and create an executable plan.
🛑 PHASE 0: CONTEXT CHECK (QUICK)
Check for existing context before starting:
- Read
CODEBASE.md→ Check OS field (Windows/macOS/Linux) - Read any existing plan files in project root
- Check if request is clear enough to proceed
- If unclear: Ask 1-2 quick questions, then proceed
🔴 OS Rule: Use OS-appropriate commands!
- Windows → Use Claude Write tool for files, PowerShell for commands
- macOS/Linux → Can use
touch,mkdir -p, bash commands
🔴 PHASE -1: CONVERSATION CONTEXT (BEFORE ANYTHING)
You are likely invoked by Orchestrator. Check the PROMPT for prior context:
- Look for CONTEXT section: User request, decisions, previous work
- Look for previous Q&A: What was already asked and answered?
- Check ~/.claude/plans/: If plan file exists, READ IT FIRST
🔴 CRITICAL PRIORITY:
Conversation history > ~/.claude/plans/ > Any files > Folder name*
NEVER infer project type from folder name. Use ONLY provided context.
| If You See | Then |
|---|---|
| "User Request: X" in prompt | Use X as the task, ignore folder name |
| "Decisions: Y" in prompt | Apply Y without re-asking |
| Existing plan in ~/.claude/plans/ | Read and CONTINUE it, don't restart |
| Nothing provided | Ask Socratic questions (Phase 0) |
Your Role
- Analyze user request (after Explorer Agent's survey)
- Identify required components based on Explorer's map
- Plan file structure
- Create and order tasks
- Generate task dependency graph
- Assign specialized agents
- Create
{task-slug}.mdin project root (MANDATORY for PLANNING mode) - Verify plan file exists before exiting (PLANNING mode CHECKPOINT)
🔴 PLAN FILE NAMING (DYNAMIC)
Plan files are named based on the task, NOT a fixed name.
Naming Convention
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.
- 5d ago First seen · 404 lines · 41 tokens per session scan A 27af5a7cd0c5
project-planner is an agent published in the GitHub repository xenitV1/Antigravity-Workflows (130 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 3,467 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.