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 glincker/claude-code-marketplace --skill backend-architectgit clone --depth 1 https://github.com/glincker/claude-code-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/glincker/claude-code-marketplace/backend-architect)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/backend-architect"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/backend-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.00017 | $0.00289 |
| Opus 5 | $0.00009 | $0.00144 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
backend-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 8d 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.
What it actually says
Backend Architect Agent
Senior backend architect agent specializing in scalable API design, database architecture, and microservices patterns.
Agent Expertise
- RESTful and GraphQL API design
- Database schema design (SQL, NoSQL)
- Microservices architecture patterns
- Event-driven architecture
- Caching strategies (Redis, Memcached)
- Message queues (RabbitMQ, Kafka)
Key Capabilities
- API Design: OpenAPI specs, endpoint structure, versioning
- Database Architecture: Schema design, indexing, migrations
- Microservices: Service boundaries, communication patterns
- Scalability: Load handling, horizontal scaling strategies
- Security: Authentication, authorization, rate limiting
Quick Commands
- "Design REST API for e-commerce platform"
- "Create database schema for social network"
- "Architect microservices for payment system"
- "Design event-driven workflow"
- "Optimize database queries for performance"
Author
GLINCKER Team
What ships with it
1 file 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.
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.
- 8d ago First seen · 43 lines · 17 tokens per session scan A 75228a92a5f1
backend-architect is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 289 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 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.
flowise-builder
Use when flowise visual LLM workflow builder — drag-drop chatflows, API endpoints, document loaders, tools. Use when working with flowise builder.
postbridge-social-manager
Use when multi-platform social media posting, scheduling, analytics, and media management via PostBridge API for TikTok, Instagram, X, LinkedIn, and Facebook. Use when working with postbridge social manager.
telegram-userbot
Use when full MTProto control of Telegram account via Telethon. DM, Voice Note, Call, Video Call, Group/Channel management, member scraping, bot cloning, outreach automation, broadcast, CRM tracking, content reposting, scheduled messaging, webhook triggers. Use for all Telegram automation as a real user (not bot API).
bullmq
Skill "bullmq" from ashish7802/awesome-api-skills, covering bullmq skill, ecosystem graph preview, recommended next skills, quick start and production patterns.
convex
Convex manages your database, server functions, and client state. You write server functions in TypeScript, and Convex automatically syncs the results to your React frontend via WebSockets.