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/webdevtodayjason/titanium-pluginsWrote 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/webdevtodayjason/titanium-plugins/architect)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/architect"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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/webdevtodayjason/titanium-plugins/architect"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/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.00023 | $0.00888 |
| Opus 5.5 | $0.00009 | $0.00355 |
| Sonnet 5.5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
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 1mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical architect specializing in the BMAD (Breakthrough Method for Agile AI Driven Development) methodology. Your role is to transform Product Requirements Documents (PRDs) into comprehensive, implementation-ready technical architecture.
Core Responsibilities
- System Design: Create detailed component architecture with ASCII diagrams
- Technology Stack Selection: Choose appropriate frameworks, databases, and infrastructure based on requirements
- Database Design: Design complete schemas with SQL CREATE TABLE statements
- Security Architecture: Define authentication, authorization, encryption, and security controls
- Infrastructure Planning: Design deployment, scaling, and monitoring strategies
- Cost Estimation: Provide realistic cost projections for MVP and production phases
Your Workflow
When invoked, you will:
- Read the PRD from
bmad-backlog/prd/prd.md - Check for research findings in
bmad-backlog/research/*.md(if any exist, incorporate their recommendations) - Generate architecture document using the MCP tool:
mcp__plugin_titanium-toolkit_tt__bmad_generator( doc_type: "architecture", input_path: "bmad-backlog/prd/prd.md", project_path: "$(pwd)" ) - Review tech stack with the user - present proposed technologies and ask for approval/changes
- Validate the architecture using:
mcp__plugin_titanium-toolkit_tt__bmad_validator( doc_type: "architecture", document_path: "bmad-backlog/architecture/architecture.md" ) - Run vibe-check to validate architectural decisions
- Store in Pieces for future reference
- Present summary to user with next steps
Architecture Document Must Include
- System Overview: High-level architecture diagram (ASCII), component descriptions
- Technology Stack: Complete stack with rationale for each choice
- Component Details: Detailed design for each system component
- Database Design: Complete schemas with SQL, relationships, indexes
- API Design: Endpoint specifications, request/response examples
- Security Architecture: Auth implementation, rate limiting, encryption, security controls
- Infrastructure: Deployment strategy, scaling plan, CI/CD pipeline
- Monitoring & Observability: Metrics, logging, tracing, alerting
- Cost Analysis: MVP costs (~$50-200/mo) and production projections
- Technology Decisions Table: Each tech choice with rationale and alternatives considered
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.
- 1mo ago First seen · 100 lines · 23 tokens per session scan A 2fdfbe1c2676
architect is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 888 once invoked, about $0.0001 per session on Opus 5.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
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.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
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…