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/ashrafmusa/agenticana/project-plannergit clone --depth 1 https://github.com/ashrafmusa/agenticanaWrote 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/ashrafmusa/agenticana/project-planner)<a href="https://agentmods.dev/agents/ashrafmusa/agenticana/project-planner"><img src="https://agentmods.dev/badge/agents/ashrafmusa/agenticana/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.03486 |
| Opus 5 | $0.00020 | $0.01743 |
| Sonnet 5 | $0.00008 | $0.00697 |
| Haiku 4.5 | $0.00004 | $0.00349 |
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 4d 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.
This is a copy
91% identical to project-planner — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 407 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 plan files: If plan file exists in workspace, READ IT FIRST
🔴 CRITICAL PRIORITY:
Conversation history > Plan files in workspace > 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 workspace | 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.
- 4d ago First seen · 407 lines · 41 tokens per session scan A 4027c6abdd1c
project-planner is an agent published in the GitHub repository ashrafmusa/agenticana (2 stars, last pushed 4d ago), licensed MIT. It adds 41 tokens to every session and 3,486 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to project-planner, differing in 27 lines, and is treated as a copy.
Other agents, from other repositories
agent_types
This document describes how the unified three-layer Device Agent architecture is implemented across different platforms. While the core framework (State, Processor, Command layers) remains consistent, each platform implements specialized agents optimized for their native control mechanisms and hierarchies.…
server_client_architecture
Device agents in UFO are partitioned into server and client components, separating high-level orchestration from low-level execution. This architecture enables safe, scalable, and flexible task execution across heterogeneous devices through the Agent Interaction Protocol (AIP).
challenger
I handle: Fact-checking, counter-hypothesis testing, verification, constructive challenge I do not handle: Implementation, code writing, architecture design — I review, not build On rejection: Specific items needing correction + verification methods provided.
Update Copilot CompletionAlgorithm
Synchronize this repository's Copilot completion behavior with a pinned microsoft/vscode commit while preserving reviewed completion effects and provenance.
Update Cli Clients
Regularly maintain certain clients.
03-Architect
Expert Architect providing guidance using Azure Well-Architected Framework principles and Microsoft best practices. Evaluates decisions against WAF pillars and generates ARM MCP-verified cost estimates.