What is saas-microservice?

A workflow for building a TypeScript SaaS microservice with domain-driven design and shared features for identity, permissions, multiple customers, auditing, and reliable event delivery. A microservice is a separately deployable backend service; SaaS means software offered to multiple customers online.

It is for scaffolding and building TypeScript SaaS backend services with APIs, domain models, access control, Docker, CI/CD, and Cloud Run deployment.

It provides a defined path from modeling the business domain to implementing, testing, securing, and deploying the service. This reduces the amount of foundation work needed before application-specific logic can be added.

saas-microservice — Skill for Claude Code by hamzaPixl

Install

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.

Any agent

npx skills add hamzaPixl/pixl-ai --skill saas-microservice

Clone the repo

git clone --depth 1 https://github.com/hamzaPixl/pixl-ai

Made for: Claude Code.

Or install pixl-crew, the plugin that ships this one along with the rest of its 93 skills, 14 agents, 6 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/saas-microservice/github.svg)](https://agentmods.dev/skills/hamzapixl/pixl-ai/saas-microservice)

Your own site

<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/saas-microservice"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/saas-microservice/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/saas-microservice"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/saas-microservice.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,164 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00083	$0.01164
Opus 5	$0.00042	$0.00582
Sonnet 5	$0.00017	$0.00233
Haiku 4.5	$0.00008	$0.00116

Measured 8d ago against content hash 3a4ad4bbcb3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

saas-microservice 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.

packages/crew/skills/saas-microservice/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Orchestrates building a complete SaaS microservice using the studio's saas stack. Scaffolds from the foundation packages and service template, then implements domain logic, API endpoints, tests, and deployment.

Studio Stack

Scaffold from: studio/stacks/saas/ (18 foundation packages + service template)

Suggested Team

architect — Domain modeling, bounded context mapping, aggregate design
backend-engineer — Entity implementation, routes, repositories
qa-engineer — Test writing, review loops
devops-engineer — Docker, CI/CD, Cloud Run deployment
security-engineer — RBAC review, security audit

Process

Phase 1: Domain Design

Run /ddd-pattern Discovery phase — analyze the domain
Run /ddd-pattern Model phase — entities, aggregates, value objects
Delegate to architect for bounded context review

Phase 2: Scaffold

Copy studio/stacks/saas/foundation/ packages (use pruning rules for minimal set)
- Important: Use rsync -a --exclude node_modules instead of cp -r to avoid broken symlinks from node_modules/.bin
Apply studio/stacks/saas/service-template/ with token replacement:
- SERVICE_NAME, SERVICE_NAME_PASCAL, SERVICE_PORT
- ENTITY_NAME, ENTITY_SLUG, ENTITY_PLURAL, ENTITY_PLURAL_SLUG
- FOUNDATION_DEPS — the full JSON dependencies block for package.json (includes @prisma/client, needed @saas-studio/* packages, and zod). Use the pruning rules in manifest.yaml to include only required foundation packages.
- ENTITIES (optional) — comma-separated list of additional entities to scaffold, e.g. Article,Category:Categories,Tag. Supports Name:Plural syntax for irregular plurals. The first entity uses the primary ENTITY_* tokens above.
Post-scaffold: After running scaffold.sh, write package.json directly if the FOUNDATION_DEPS token needs multi-line content (the tokens file is line-based, so complex JSON should be written as a post-processing step).
Run bun install and verify clean build

Read the full file on GitHub · 89 lines

Files

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.

reference.md 69 KB

Changes

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 · 89 lines · 83 tokens per session scan A 3a4ad4bbcb3e

Subscribe to this mod's changes

saas-microservice is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 5mo ago), licensed MIT. It adds 83 tokens to every session and 1,164 once invoked, about $0.0004 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.

Backend and APIs CI and CD Containers DevOps and cloud

deploy

Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.

oliver-kriska/claude-elixir-phoenix · 46 tokens

bunjs-production

Use when deploying Bun.js to production, containerizing with Docker, setting up AWS ECS/Fargate, implementing Redis caching, hardening security, or configuring CI/CD pipelines. See bunjs for basics, bunjs-architecture for patterns.

MadAppGang/claude-code · 52 tokens

data-processing

Process JSON with jq and YAML/TOML with yq. Filter, transform, query structured data efficiently. Triggers on: parse JSON, extract from YAML, query config, Docker Compose, K8s manifests, GitHub Actions workflows, package.json, filter data.

NeverSight/learn-skills.dev · 58 tokens

nestjs-monorepo-scaffold

Turborepo + NestJS + Drizzle + BullMQ monorepo scaffolding — project structure, shared types, workspace config, Docker, CI/CD, and new feature bootstrapping.

me-cedric/agent-compass · 46 tokens

deployment-patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

affaan-m/ECC · 41 tokens

enterprise

Enterprise-grade systems with microservices, Kubernetes, Terraform, and AI Native methodology. For multi-feature initiatives spanning a release timeline, combine with /sprint master-plan (v2.1.13) to group features into a single 8-phase sprint container with shared scope/budget and 4 auto-pause triggers…

ww-w-ai/bkit-claude-code · 106 tokens