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 agentmods add skills/telus-labs/stagecraft/platform-deploynpx skills add telus-labs/stagecraft --skill platform-deploygit 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-deploy)<a href="https://agentmods.dev/skills/telus-labs/stagecraft/platform-deploy"><img src="https://agentmods.dev/badge/skills/telus-labs/stagecraft/platform-deploy.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 | $0.00038 | $0.00737 |
| Opus 5 | $0.00019 | $0.00368 |
| Sonnet 5 | $0.00008 | $0.00147 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
platform-deploy 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 4d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Deploy Task (Stage 8)
Use this skill when you are the Platform Developer executing the Stage 8
deploy stage. Stage 8 is adapter-driven. Read .devteam/config.yml, discover
which adapter the project has selected, and follow that adapter's instructions
in .devteam/adapters/<adapter>.md. If no adapter is configured, default to
local and follow .devteam/adapters/local.md.
Step 0 — Common preconditions (every adapter)
- PM sign-off. Read
pipeline/gates/stage-07.json. If"pm_signoff": trueis absent or false: write"status": "ESCALATE"with reason "PM sign-off missing — cannot deploy" and halt. If"deploy_requested": false, do not ask the Principal whether to deploy. Treat it as an explicit instruction that no external deployment was requested; use thelocaladapter, run/record local verification, and markadapter_result.external_deploy: false. - Runbook. Confirm
pipeline/runbook.mdexists and contains at minimum a## Rollbackand## Health signalssection. If missing: write"status": "ESCALATE"with reason "Runbook required for Stage 8". - Config. Read
.devteam/config.yml. Finddeploy.adapter. If missing, uselocal. Accept one of:local,docker-compose,kubernetes,terraform,cloud-run,gizmos,npm,custom. Unknown adapter: write"status": "FAIL"with reason "Unknown deploy adapter." Do not escalate for a missing adapter;localis the safe default.
Step 1 — Load adapter instructions
Read .devteam/adapters/<adapter>.md and follow the adapter's numbered procedure.
Adapters are authoritative for their own deploy story.
Step 2 — Write outputs
Every adapter's procedure ends with writing two artefacts:
pipeline/deploy-log.md: human-readable record of the deploy, including a**Runbook**: pipeline/runbook.md §<section>line that points a future on-call engineer at the recovery procedure.pipeline/gates/stage-08.json: gate with the baseline fields required by.devteam/rules/gates-core.mdplus:{ "deploy_adapter": "<name>", "environment": "<env>", "smoke_test_passed": true, "runbook_referenced": true, "adapter_result": { /* adapter-specific */ } }
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.
- 4d ago First seen · 66 lines · 38 tokens per session scan A ad552b4e382d
platform-deploy is a skill published in the GitHub repository telus-labs/stagecraft (6 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 737 once invoked, about $0.0002 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-31.
Other skills, from other repositories
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
semantix-guide
Troubleshoot and configure Semantix capabilities: Skills (project/custom/global/builtin priority, discovery dirs), Commands (override order, /dir:file naming), Hooks (11 events, automatic project loading, matchers, timeouts), MCP (semantix-agent.toml + .mcp.json + plugin packages, autostart), plugin packages…
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
intuitive-flow
Stable execution/change router after an approved plan, preflight contract, or tiny concrete task. Refactor-shaped work delegates to intuitive-refactor, and durable work runs through staged planning, review, GSD handoff, implementation, cleanup, and verification while keeping plan ledgers and active capsules compact by…
intuitive-preflight
Turn a vague task, plan, issue, or "LGTM/go ahead" request into an approval-ready preflight contract before implementation starts. Use when the user wants prompt preflight, clearer scope, non-goals, context package, acceptance criteria, definition of done, verification, stop gates, the exact execution command, or…
intuitive-squash
Squash local GSD or agent-generated commit history into a clean, reviewable story while preserving important fixes. Use when the user asks to squash commits, clean git history, compress phase commits, prepare a branch before PR, compare aggressive vs moderate squash options, or preserve hotfix/security commits during…