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 athola/claude-night-market --skill architecture-paradigm-client-servergit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/architecture-paradigm-client-server)<a href="https://agentmods.dev/skills/athola/claude-night-market/architecture-paradigm-client-server"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigm-client-server/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/athola/claude-night-market/architecture-paradigm-client-server"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigm-client-server.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.00034 | $0.00903 |
| Opus 5.5 | $0.00014 | $0.00361 |
| Sonnet 5.5 | $0.00007 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
architecture-paradigm-client-server 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 24d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Client-Server and Peer-to-Peer Paradigms
When to Employ This Paradigm
- For traditional applications that have centralized services, such as web or mobile clients communicating with backend APIs.
- For systems exploring decentralized or "offline-first" capabilities that rely on peer-to-peer synchronization.
- To formally document trust boundaries, client-server version negotiation, and API evolution strategies.
When NOT To Use
- Systems with no network boundary between UI and logic (use
archetypes:architecture-paradigm-modular-monolith) - Choosing among paradigms in the first place (use
archetypes:architecture-paradigms)
Adoption Steps
- Define Responsibilities: Clearly delineate which logic and data reside on the client versus the server, with the goal of minimizing duplication.
- Document the Contracts: Formally document all APIs, data schemas, authentication flows, and any capability negotiation required for handling different client versions.
- Plan for Version Skew: Implement a strategy to manage different client and server versions, such as using feature flags,
Acceptheaders for content negotiation, or semantic versioning for APIs. - Address Connectivity Issues: If the application is not purely client-server, design for intermittent connectivity. This may involve implementing offline caching, data synchronization protocols, or peer discovery and membership services.
- Secure All Communications: Enforce the use of TLS for all data in transit. Implement authorization policies, rate limiting, and detailed telemetry for every endpoint.
Key Deliverables
- An Architecture Decision Record (ADR) that covers the roles of clients, servers, and peers, defines the trust boundaries, and outlines deployment assumptions.
- Formal API or protocol specifications, along with a suite of compatibility tests.
- Runbooks detailing the coordination required for rollouts, such as client release waves, backward-compatibility support, or operational procedures for a peer-to-peer network.
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.
- 24d ago Changed · -4 lines 18a62ab09337
- 1mo ago First seen · 77 lines · 34 tokens per session scan A 019f607d59a6
architecture-paradigm-client-server is a skill published in the GitHub repository athola/claude-night-market (343 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 903 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-09-03.
Other skills, from other repositories
microservices-expert
Expert-level microservices architecture, patterns, service mesh, and distributed systems. Use when the user mentions distributed systems, service mesh, or architecture, or when the task involves Microservices Principles, Architecture Patterns, Communication, or Data Management.
system-design
Production system design — scalability patterns, trade-off analysis, database selection, caching strategy, API design, and architecture decisions.
data-intensive-patterns
Generate and review data-intensive application code using patterns from Martin Kleppmann's "Designing Data-Intensive Applications." Use this skill whenever the user asks about data storage engines, replication, partitioning, transactions, distributed systems, batch or stream processing, encoding/serialization…
microservices-patterns
Generate and review microservices code using patterns from Chris Richardson's "Microservices Patterns." Use this skill whenever the user asks about microservices architecture, wants to generate service code, design distributed systems, review microservices code, implement sagas, set up CQRS, configure API gateways…
system-design-interview
Apply system design principles from System Design Interview by Alex Xu. Covers scaling (load balancing, DB replication, sharding, caching, CDN), estimation (QPS, storage, bandwidth), the 4-step framework, and 12 real designs: rate limiter, consistent hashing, key-value store, unique ID generator, URL shortener, web…
distributed-feasibility-checker
Evaluate whether a system should adopt distributed architecture by systematically checking against the 8 Fallacies of Distributed Computing and assessing team/operational readiness. Use this skill whenever the user is considering microservices, debating monolith vs distributed, hearing "let's use microservices,"…