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 saemihemma/lead-producer-oss --skill team-architecture-reviewgit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/team-architecture-review)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/team-architecture-review"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-architecture-review/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/saemihemma/lead-producer-oss/team-architecture-review"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/team-architecture-review.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.00038 | $0.00593 |
| Opus 5 | $0.00019 | $0.00296 |
| Sonnet 5 | $0.00008 | $0.00119 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
team-architecture-review 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 12d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review Team
Purpose
Evaluate whether system shape is structurally sound, scalable, secure, strategically sensible, and realistic to ship. Prioritize by reversibility.
Composition
- role-software-architect: structure, boundaries, contracts, decomposition
- role-cto: strategic fit, long-term cost, organizational implications
- role-scalability-engineer: load paths, bottlenecks, scaling risk
- role-security-engineer: threat surface, security constraints, blast radius
- role-technical-product-manager: delivery feasibility, dependencies, migration risk
- Synthesis: conflict handling, acceptance
Use When
- Designing new system or major subsystem
- Evaluating migration, decomposition, hard-to-reverse contract
- Reviewing API/service boundaries or major data-model choices
- Post-incident architecture review
Do NOT Use When
- Small implementation review or routine refactor
- Product prioritization or roadmap value
- Deployment-only with no architecture decision
- Narrow interface shape fitting
workflow-design-interface-options
Required Diagram
Every review must ship with a verified Mermaid diagram:
- Diagram what IS, not aspirational
- Label services, stores, external dependencies, data flows
- Distinguish sync/async paths when it matters
- Validate against code or evidence before accepting
Workflow
- Load truth sources: architecture docs, code reality, constraints, and what already exists.
- Run specialist perspectives in parallel; sequence only when dependent.
- Rank findings by reversibility: hardest-to-change first.
- Call out what is not in scope and the top failure modes.
- Resolve conflicts explicitly.
- Synthesize for acceptance.
Default Output
ARCHITECTURE REVIEW
===================
System Shape: existing components, boundaries, ownership, major contracts
Risk Review: scalability, security, migration/rollback risks
Failure Modes: top failure modes, out-of-scope work
Reversibility: hardest-to-change decisions, attention order
Artifact: verified Mermaid diagram
Verdict: Accept / Rework / Escalate, open questions
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.
- 12d ago First seen · 68 lines · 38 tokens per session scan A ee4de5122d25
team-architecture-review is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 593 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…