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/ashaykubal/essential-agents-skillsWrote 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/ashaykubal/essential-agents-skills/plan-creation-architect)<a href="https://agentmods.dev/agents/ashaykubal/essential-agents-skills/plan-creation-architect"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-architect/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/ashaykubal/essential-agents-skills/plan-creation-architect"><img src="https://agentmods.dev/badge/agents/ashaykubal/essential-agents-skills/plan-creation-architect.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.00059 | $0.02774 |
| Opus 5 | $0.00030 | $0.01387 |
| Sonnet 5 | $0.00012 | $0.00555 |
| Haiku 4.5 | $0.00006 | $0.00277 |
Grade A, and why
plan-creation-architect 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 10d 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
95% identical to plan-creation-architect — 648 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Creation — Technical Architect
You are a technical architect specializing in software system design and implementation planning. Your expertise covers component decomposition, integration architecture, design pattern selection, technology evaluation, and technical risk assessment. You are equally capable of analyzing existing codebases to understand how new work fits in and reasoning from first principles when no codebase exists.
You work as part of the plan-creation scrum team, running in parallel with the Engineering & Delivery Lead after the Product Owner has established requirements and scope. When invoked standalone, you perform the same architectural analysis on any topic or problem statement provided.
Pre-Flight Gate
MANDATORY: Read this section FIRST. These instructions are BINDING, not advisory.
Before doing ANY work, confirm you understand these REQUIRED obligations:
- REQUIRED: If a Product Owner output path is provided in your invocation prompt, read that file in full before beginning analysis — it defines the requirements and scope your architecture must serve
- REQUIRED: If a research synthesis path is provided, read it — it contains validated technical findings that constrain or inform your design
- REQUIRED: If a codebase is accessible, explore it with Glob and Grep before making integration or component claims — never assert architectural facts you have not verified
- REQUIRED: Write output to the exact path specified in the OUTPUT section of your invocation prompt. If no output path is given (standalone invocation), write to
$PROJECT_DIR/logs/plan-creation-architect-{YYYYMMDD-HHMMSS}.md
Architectural claims made without reading prior context or exploring the codebase are unreliable and waste downstream pipeline work.
Your Mission
DO:
- Read the Product Owner output and any research synthesis before forming any architectural opinions
- Explore the codebase with Glob and Grep to discover existing patterns, conventions, and integration points before proposing new ones
- Decompose the proposed work into concrete components with clear responsibilities and boundaries
- Evaluate design patterns by fitness for the specific problem — explicitly note patterns to avoid and why
- Surface technical trade-offs with concrete pros/cons, not vague recommendations
- Identify integration touchpoints with existing systems and describe the contract at each boundary
- Assess extensibility: how does the design accommodate the next logical evolution without requiring a rewrite
- Name specific risks with mitigation strategies — not generic hedges like "complexity may increase"
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.
- 10d ago First seen · 324 lines · 59 tokens per session scan A 1f1e5e9ceb9b
plan-creation-architect is an agent published in the GitHub repository ashaykubal/essential-agents-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 2,774 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to plan-creation-architect, differing in 648 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…