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 synaptiai/synapti-marketplace --skill architecture-patternsgit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/architecture-patterns)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/architecture-patterns"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/architecture-patterns/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/synaptiai/synapti-marketplace/architecture-patterns"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/architecture-patterns.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.00066 | $0.00975 |
| Opus 5 | $0.00033 | $0.00487 |
| Sonnet 5 | $0.00013 | $0.00195 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
architecture-patterns 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 today.
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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Patterns
Contract
Iron law: design architecture from functionality, not to functionality — a component that cannot be traced to a user, admin, or system flow is deleted. Invoked by /flow:design Phase 1 (map flows), Phase 2 (C4 level, coupling review, design proposal), and Phase 4 (decision record). Returns the enumerated flows, a coupling analysis with red flags, a proposal (components, responsibilities, dependencies, data flow, API surface) at the right C4 level, and a decision record with context, options, trade-offs, decision, consequences, non-goals, and failure modes. Permitted skips: none — a record without non-goals and failure modes is incomplete and does not ship; failure modes may be deferred only where /flow:design marks them optional.
Map Flows First
Track four tasks: map flows, coupling analysis, design proposal, decision documentation. First enumerate user flows (what the user does, step by step), admin flows (operator actions), and system flows (cron, webhooks, events). Each is trigger, steps, outcome; every component must serve at least one.
C4 Level
Context, Containers, Components, or Code — start at the highest relevant level and zoom in only when needed; most design discussion happens at Components. Level guide in architecture-decision-record.md.
Coupling Analysis
Check actual imports (grep -rn "import\|require\|from " --include="*.{ts,js,tsx,jsx,py,rb}" -l; look for A imports B and B imports A). Red flags:
- Circular dependencies — break with interfaces or events.
- God objects — one module imported by >50% of files; split by responsibility.
- Hidden coupling — shared mutable state, globals, implicit ordering.
- Shotgun surgery — one feature change touches 5+ unrelated files.
Dependencies flow one way: UI → Application → Domain, with Infrastructure depending inward; Domain depends on nothing. Never Domain → UI or Domain → Infrastructure. Endpoints follow user flows (one per user action, not per table), version only for unavoidable breaking changes, and validate at the boundary.
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.
- today Changed · -123 lines ec4d511ef0a8
- 6d ago First seen · 186 lines · 66 tokens per session scan A a23780bfc6e5
architecture-patterns is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 975 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.