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 telus-labs/stagecraft --skill platform-buildgit clone --depth 1 https://github.com/telus-labs/stagecraftWrote 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/telus-labs/stagecraft/platform-build)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/platform-build"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/platform-build/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/telus-labs/stagecraft/platform-build"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/platform-build.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.00036 | $0.00747 |
| Opus 5.5 | $0.00014 | $0.00299 |
| Sonnet 5.5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
platform-build 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -i http://localhost/api/health` How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Build Task (Stage 4)
Use this skill when you are the Platform Developer executing the Stage 4 build stage — setting up infra, CI, and the deploy rails for a new feature.
Procedure
-
Read
pipeline/design-spec.md— set up infra, CI, and root toolchain config to support what's being built. -
Append an
## Assumptionsblock topipeline/context.mdfor non-obvious infra choices (ports, volumes, healthcheck targets) per coding-principles §1. Write the Plan preamble at the top ofpipeline/pr-platform.mdper §4. -
Write or update
docker-compose.ymlin the project root:- Define a service for each component in the design spec
- Add a
healthcheck:to every HTTP service sodocker compose up --waitworks - Use
.envfor all secrets and environment-specific values — never hardcode - Mount source directories as volumes for local dev hot-reload where appropriate
-
Write or update any supporting infra/toolchain config (
.env.example, nginx config,package.jsonscripts, lockfiles, ESLint/TypeScript config, Docker/compose files, etc.). Root package-manager scripts and shared toolchain config are platform-owned unless the design spec or a Principal ruling assigns them elsewhere. Ifnpm run lintis missing, add the script and any minimal config needed for Stage 4a to run it mechanically. Keep source-code changes insidesrc/infra/; cross-boundary edits need aCONCERN:line first (coding-principles §3). -
Finish
pipeline/pr-platform.md. Include## Out of Scope — Noticed. Also:-
## Verify— required before writing a PASS gate. One bullet per infrastructure criterion you claim to have satisfied, in this exact shape:## Verify - **AC-7**: docker-compose brings the stack up cleanly - `docker compose up --wait` - → `Network created`, `Container api healthy`, `Container db healthy`, exit 0 after 14s - **AC-8**: nginx forwards /api to backend on port 3000 - `curl -i http://localhost/api/health` - → `HTTP/1.1 200 OK`, body `{"status":"ok"}`, no nginx 502
-
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 First seen · 57 lines · 36 tokens per session scan A d6bea2971c68
platform-build is a skill published in the GitHub repository telus-labs/stagecraft (7 stars, last pushed 22d ago), licensed MIT. It adds 36 tokens to every session and 747 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other skills, from other repositories
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
agenticx-deployer
Guide for deploying AgenticX agents to production including Docker containerization, Kubernetes orchestration, Volcengine AgentKit cloud deployment, and API server setup. Use when the user wants to deploy agents, containerize applications, set up Kubernetes, configure cloud deployment, or run the AgenticX API server…
gcp-essentials
Use when running a small product on core Google Cloud via the gcloud CLI: a project, Cloud Run deploys, a locked-down Cloud Storage bucket, managed Cloud SQL, and least-privilege IAM wiring them together. NOT AWS (that is aws-essentials), NOT the CI pipeline that ships the image (that is deployment), NOT Postgres…
kubernetes
Kubernetes operations expert for kubectl, pods, deployments, and debugging.
agent-cloud-architect
Specialist subagent: Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes…
huawei-cce
Use when creating or managing CCE Kubernetes clusters. Covers cluster creation, node pools, SWR registry, autoscaling. Triggers: CCE, Kubernetes, K8s, cluster, node pool, container, SWR. NOT for: serverless functions (use huawei-functiongraph), serverless containers (use huawei-cce for CCI redirect).