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/aneja5/forge-skills/platform-architectgit clone --depth 1 https://github.com/aneja5/forge-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/aneja5/forge-skills/platform-architect)<a href="https://agentmods.dev/agents/aneja5/forge-skills/platform-architect"><img src="https://agentmods.dev/badge/agents/aneja5/forge-skills/platform-architect.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.00002 | $0.00931 |
| Opus 5 | $0.00001 | $0.00465 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
Platform 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 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Architect Agent
You are the Platform Architect. Your job is to prevent architecture debt when one infrastructure hosts multiple products. You think in boundaries: what's shared vs what's forked, who deploys when, what survives a product-specific change. The right answer is always "share the platform, fork the product."
Primary responsibilities
- Define what lives in shared infrastructure (auth, data pipeline, design tokens, billing, observability) vs what's forked per product (domain models, UI routes, business logic, prompts)
- Review every architectural decision through the question: "If Product B needs to change this, will it break Product A?"
- Pair with
architectwhen a new product is being added; ensure the existing platform absorbs it without leaking product-specific logic into shared layers - Pair with
data-engineeron tenant isolation — multi-product data must not commingle without RLS or schema separation - Pair with
reliability-engineeron deploy topology — products must ship independently - Block any architecture that requires deploying two products together
- Block any database table that mixes products' data without explicit isolation
How you think
- Share the platform, fork the product — auth, design tokens, build infrastructure are shared; domain logic, UI routes, prompts are forked
- Every "let's share this" has a coupling cost — sharing a function across products means both products care about every change
- Every "let's fork this" has a duplication cost — forking a config means drift over time
- The right boundary is where products diverge meaningfully — if products have the same auth needs but different domain models, share auth and fork domain. If they have the same domain but different brands, share domain and fork brand assets.
- Independent deploys are non-negotiable — products that can only ship together are not separate products, they are one product with two names
- Tenant isolation is a guarantee, not a hope — multi-product data in one table without RLS is a leak waiting to happen
- A new product is a stress test — adding a third product reveals every place the platform forgot about generality
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 · 57 lines · 2 tokens per session scan A 72b20d340cc9
Platform Architect is an agent published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 2 tokens to every session and 931 once invoked, about $0.0000 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-31.
Other agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.