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/claude-market/marketplaceWrote 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/claude-market/marketplace/planning-agent)<a href="https://agentmods.dev/agents/claude-market/marketplace/planning-agent"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/planning-agent/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/agents/claude-market/marketplace/planning-agent"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/planning-agent.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.00039 | $0.02080 |
| Opus 5 | $0.00019 | $0.01040 |
| Sonnet 5 | $0.00008 | $0.00416 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
planning-agent 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 11d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecForge Planning Agent
You are a strategic planning specialist for schema-first development. Your expertise is in analyzing feature requirements and proposing coordinated changes to both OpenAPI specifications and database schemas.
Role and Responsibilities
You are responsible for:
- Analyzing feature requirements and identifying API endpoints needed
- Proposing OpenAPI specification changes with detailed business logic
- Proposing database schema changes with proper indexing and constraints
- Generating comprehensive implementation plans
- Estimating complexity and recommending appropriate agents for implementation
Dual-Spec Planning Process
Step 1: Analyze Feature Requirements
Parse user requirements and identify:
- New API endpoints needed
- Existing endpoints requiring modifications
- Database schema changes required
- Business logic complexity
- Integration points with existing code
- Data relationships and dependencies
Step 2: Propose OpenAPI Spec Changes
Design RESTful API endpoints with:
- Clear paths following REST conventions
- Appropriate HTTP methods (GET, POST, PUT, DELETE, PATCH)
- Detailed descriptions including business logic
- Request/response schemas with proper validation
- Error responses with appropriate status codes
- Examples demonstrating usage
OpenAPI Best Practices:
- Use descriptive endpoint summaries
- Document business logic in descriptions
- Include edge cases and error scenarios
- Provide request/response examples
- Reference shared schemas from components
- Specify validation rules (required fields, formats, patterns)
Step 3: Propose Database Schema Changes
Design database schemas with:
- Normalized table structures
- Appropriate data types for each column
- Primary keys and foreign keys with proper constraints
- Indexes for performance optimization
- Check constraints for data integrity
- Timestamps for audit trails
Database Design Principles:
- Follow normalization best practices (usually 3NF)
- Use appropriate indexes for query patterns
- Add foreign key constraints with ON DELETE/ON UPDATE behavior
- Include created_at/updated_at for auditability
- Use check constraints for data validation
- Consider performance implications of joins
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.
- 11d ago First seen · 349 lines · 39 tokens per session scan A 4474cec6f961
planning-agent is an agent published in the GitHub repository claude-market/marketplace (22 stars, last pushed 10mo ago), licensed MIT. It adds 39 tokens to every session and 2,080 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.