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 cenconq25/claude-code-app-studio --skill team-backendgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/team-backend)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/team-backend"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/team-backend/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/cenconq25/claude-code-app-studio/team-backend"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/team-backend.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.00049 | $0.02076 |
| Opus 5 | $0.00024 | $0.01038 |
| Sonnet 5 | $0.00010 | $0.00415 |
| Haiku 4.5 | $0.00005 | $0.00208 |
Grade A, and why
team-backend scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Hit each new endpoint with a test client (curl / HTTPie / Bruno How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Backend
The data-side counterpart to /team-frontend. Coordinates the roles
that own the API contract, the persistence layer, the offline sync
strategy, the push channel, and any Firebase-style BaaS surface.
Team Composition
- backend-engineer — feature owner on the server side.
- api-designer — request / response shape, versioning, error conventions, OpenAPI spec.
- database-specialist — schema, indexes, migrations, query plans.
- offline-sync-specialist — local cache, conflict resolution, outbox pattern, retry semantics.
- push-notification-specialist — APNs / FCM topology, device-token lifecycle, payload contracts.
- firebase-specialist (optional) — Auth, Firestore, RemoteConfig, Crashlytics, Analytics, Cloud Functions.
Spawn each via Task. Parallelize where dependencies allow.
Phase 1: Resolve Feature Scope
Parse argument:
--feature=<name>-> glob related stories.--epic=<slug>-> readproduction/epics/[slug]/.- No argument -> ask the user.
Read in parallel:
- The PRD under
design/prd/. - Governing ADRs in
docs/architecture/(esp. data, sync, auth). - Design package if a UI exists (
design/packages/). - Existing API specs in
docs/api/or wherever OpenAPI lives. - The current data schema docs.
Decide which roles are needed. Not every feature needs every role.
Phase 2: API Contract via api-designer
Spawn api-designer via Task. Prompt template:
Feature: [name]. PRD: [path]. Existing API conventions: [paths]. Design endpoints: routes, methods, request bodies, response bodies, status codes, error envelopes, auth requirements, rate-limit implications, cursor / pagination semantics, idempotency keys for mutations. Output an OpenAPI fragment plus a written summary. Flag any deviation from existing conventions and require justification.
Render the contract. Use AskUserQuestion to approve.
This contract is the source of truth for the rest of the cycle — both /team-frontend's state layer and /team-backend's database specialist depend on it.
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.
- 6d ago First seen · 290 lines · 49 tokens per session scan A 150776ac2ec4
team-backend is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 2,076 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
azure-postgres-ts
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL…
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
supabase-node
Express/Hono with Supabase and Drizzle ORM.