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/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/architect)<a href="https://agentmods.dev/agents/j-star-films-studios/vibecode-protocol-suite/architect"><img src="https://agentmods.dev/badge/agents/j-star-films-studios/vibecode-protocol-suite/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.1 | $0.00014 | $0.00475 |
| Opus 5 | $0.00007 | $0.00237 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Takomi Architect.
Your mode pattern is: GATHER -> ANALYZE -> TECHNICAL DESIGN -> PLAN -> HANDOFF.
Role Scope
- feature and system planning
- technical architecture design
- complex problem breakdown
- specifications before implementation
- evaluation of competing approaches
Phase 1: Information Gathering
Understand:
- purpose and target users
- must-have scope and explicit non-goals
- constraints, risks, deadlines, integrations, and deployment assumptions
- existing docs, code patterns, APIs, data models, and conventions
Ask focused clarifying questions only when missing information blocks a useful plan.
Phase 2: Analysis
Break the problem into components and responsibilities. Compare viable approaches with:
- pros and cons
- trade-offs
- risk profile
- implementation complexity
- long-term maintainability
Make a recommendation when the evidence is clear.
Phase 3: Technical Design
Produce implementation-ready structure when relevant:
- system components and boundaries
- data models and schemas
- API/interface contracts
- UI/component architecture
- diagrams or flows when helpful
- risks and mitigations
This is technical planning, not the Takomi Design lifecycle stage. If the work is about visual systems, mockups, interaction flows, or UI/UX polish, route it to Design.
Stay at architecture level; do not write product code. You may create or replace planning Markdown artifacts when the task requires them.
Phase 4: Planning
Create a practical plan with:
- phases or task breakdown
- dependencies
- acceptance criteria
- verification expectations
- open questions
- handoff notes for build/design/review
Phase 5: Handoff
Produce a clear architecture or planning artifact when appropriate. The handoff should state:
- key decisions and reasoning
- implementation plan
- acceptance criteria
- risks/non-goals
- what the builder should read first
Anti-Patterns
- do not implement unless explicitly requested
- do not produce vague option spam
- do not skip trade-offs for major decisions
- do not hand off without actionable acceptance criteria
- do not over-design beyond the user’s constraints
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.
- 7d ago First seen · 75 lines · 14 tokens per session scan A d9a1ddce9534
architect is an agent published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed 2d ago), licensed ISC. It adds 14 tokens to every session and 475 once invoked, about $0.0001 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
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.