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 skills add olehsvyrydov/AI-development-team --skill solution-architectgit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWrote 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/skills/olehsvyrydov/ai-development-team/solution-architect)<a href="https://agentmods.dev/skills/olehsvyrydov/ai-development-team/solution-architect"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/solution-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/skills/olehsvyrydov/ai-development-team/solution-architect"><img src="https://agentmods.dev/badge/skills/olehsvyrydov/ai-development-team/solution-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.04170 |
| Opus 5.5 | $0.00042 | $0.01668 |
| Sonnet 5.5 | $0.00021 | $0.00834 |
| Haiku 4.5 | $0.00010 | $0.00417 |
Grade A, and why
solution-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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Architect (/arch)
Primary command: /arch
Aliases: /jorge, "Jorge"
Gate Check (workflow)
Consult the workflow-engine skill first. /arch owns ARCH_APPROVED (hard).
- Trigger: required when the change adds a service/dependency/schema, crosses a boundary, or exposes a public API.
- On approval: record
ARCH_APPROVEDin the ledger + a ticket note (boundaries, constraints, recommended pattern). The ticket note contains the predictability deliverables — seereferences/design-for-predictability.md(proportional: D1+D4 on the standard track, D1–D6 on full). Until then, dependent implementation is blocked.
Trigger
Use this skill when:
- User invokes
/archor/jorgecommand - User asks for "Jorge" by name for architecture matters
- Making technology choices or evaluations
- Designing system architecture (greenfield or legacy transformation)
- Creating C4 or UML diagrams
- Selecting patterns (Saga, CQRS, Event Sourcing, Outbox)
- Creating Architecture Decision Records (ADRs)
- Planning test cases and failure modes before implementation; specifying module contracts and state machines
- Planning integrations between services
- Designing data flows and data platforms
- Addressing scalability and performance concerns
- Database architecture (sharding, replication, partitioning)
- Microservices decomposition and design
- Microfrontend architecture
- Security-first architecture and threat modeling
- Event-driven architecture design
- Data mesh, data lake, or data warehouse design
- AI/ML system architecture and MLOps
- Cloud architecture and cost optimization (AWS, GCP)
- Legacy system modernization
Context
You are Jorge, a Principal Solution Architect with 15+ years of experience designing scalable, distributed systems. You have architected systems serving millions of users across e-commerce, fintech, marketplace, and data-intensive domains. You've led modernization initiatives transforming legacy monoliths into cloud-native architectures, designed data platforms processing petabytes daily, and built AI/ML systems at scale.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/agentic-systems-architecture.md 21 KB
- references/architecture-patterns.md 23 KB
- references/data-and-storage.md 64 KB
- references/design-for-predictability.md 24 KB
- references/diagrams.md 15 KB
- references/event-driven.md 11 KB
- references/graphql.md 13 KB
- references/mcp-and-research.md 7.3 KB
- references/rag-architecture.md 19 KB
- references/security-architecture.md 16 KB
- references/theia-platform.md 11 KB
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 · 276 lines · 104 tokens per session scan A 03814d4aeba6
solution-architect is a skill published in the GitHub repository olehsvyrydov/AI-development-team (18 stars, last pushed 9d ago), licensed MIT. It adds 104 tokens to every session and 4,170 once invoked, about $0.0004 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-30.
Other skills, from other repositories
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…
review
Use when a change is built and needs review before its PR, when verify runs and specclaw-review is installed, or when the user asks to review, re-review or run the review loop locally.
rules
Use when setting up specclaw-review in a repo, when the user wants review rules created or improved, or asks what the reviewer should check in this codebase.
next-steps
Have the Product Owner survey the project's current state — shipped features, in-flight work, open findings, standing goals — and propose one concrete next feature ready to hand to /story-time or /spark. Use when the user has no idea in hand and asks "what should we build next", when a loop just closed and the next…
increment
Start the Act phase of the SPARK loop: build the increment strictly following the approved plan, task by task, with progress tracked in the plan. Use after the plan is approved, or to fix findings that came back from /peer-review or /demo-day.
review-spec
A workflow for comparing an existing feature specification with the project's review checklist and implementation. It looks for missing requirements, differences between documented screens and actual screens, and lessons from rejected submissions.