Borrowing it
Nothing to install: this file belongs to nikzlabs/shipit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nikzlabs/shipit/main/.agents/skills/deployment-architecture/SKILL.mdgit clone --depth 1 https://github.com/nikzlabs/shipitWrote 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/nikzlabs/shipit/deployment-architecture)<a href="https://agentmods.dev/skills/nikzlabs/shipit/deployment-architecture"><img src="https://agentmods.dev/badge/skills/nikzlabs/shipit/deployment-architecture/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/nikzlabs/shipit/deployment-architecture"><img src="https://agentmods.dev/badge/skills/nikzlabs/shipit/deployment-architecture.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.00042 | $0.01036 |
| Opus 5.5 | $0.00017 | $0.00414 |
| Sonnet 5.5 | $0.00008 | $0.00207 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
deployment-architecture 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 1mo 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Architecture
ShipIt uses automatic deployments via platform Git integration — no manual deploy button or ShipIt-managed build. Users connect their repo to Vercel, Cloudflare Pages, or Netlify once, and every push triggers the platform's native deploy pipeline. Since ShipIt auto-pushes after every agent turn, deploys happen automatically.
How It Works
- User imports their GitHub repo on a hosting platform (Vercel, Cloudflare Pages, Netlify)
- ShipIt's auto-push after agent turns triggers the platform's deploy pipeline
- The platform creates GitHub Deployments on each deploy
- ShipIt's
PrStatusPollerfetches deployment status via the GitHub GraphQL API - Deployment status (URLs, state) appears in the PR lifecycle card
Components
| Component | Location | Role |
|---|---|---|
PrStatusPoller |
src/server/orchestrator/pr-status-poller.ts |
Polls GitHub for PR + deployment status |
GraphQL selection + mapDeploymentState |
src/server/orchestrator/pr-status-parser.ts |
The deployments query fields and the GitHub-state → ShipIt-state mapping |
GitHubDeploymentStatus |
src/server/shared/types/deployment-types.ts |
Type for deployment status data |
PrStatusSummary.deployments |
src/server/shared/types/github-types.ts |
Deployment data on PR status |
DeploymentStatusRow |
src/client/components/PrLifecycleCard/indicators/DeploymentStatusRow.tsx |
UI row showing deploy status, rendered from phases/OpenPhase.tsx |
| PR tab Status section | src/client/components/pr-detail/PrStatusSection.tsx |
The second render site — same rows, without the "via" attribution |
| Project Settings "Deployments" tab | src/client/components/ProjectSettings.tsx |
Setup guide with platform links |
Deployment Status Tracking
The PR status GraphQL selection includes commit.deployments(last: 3) on the PR's head commit —
so only the three most recent deployments of that commit are ever fetched. Each deployment
includes:
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.
- 1mo ago Changed · +19 lines 4b837438d4f8
- 1mo ago Changed 855ed6a884c2
- 1mo ago First seen · 61 lines · 42 tokens per session scan A c7085d4b7e69
deployment-architecture is a skill published in the GitHub repository nikzlabs/shipit (9 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 1,036 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
moai-platform-deployment
Deployment and hosting platform specialist covering Vercel, Railway, and Convex. Use when deploying applications, configuring edge functions, setting up continuous deployment, or managing serverless infrastructure.
moai-platform-database-cloud
Cloud database platform specialist covering Neon (serverless PostgreSQL), Supabase (PostgreSQL 16 with real-time), and Firebase Firestore (NoSQL with offline sync). Use when choosing or setting up cloud databases.
stack-baseline
The pinned default technology stack for SMB Product-Builder products. One source of truth so the architect, app-scaffolder, auth-engineer, and senior-dev never re-decide the stack per build — they build ON it. Covers framework, ORM/DB, auth, UI, payments/email/SMS, files, jobs, testing, hosting, and observability…
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.
blueprint-from-collection-import
Move the copied collection's records into Postgres and the files they point at into Storage, proven on a freshly reset local database.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations. Not for: a loom orchestration job or CI pipeline job — see loom-ci-cd.