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 starter-series/create-starter --skill deploy-setupgit clone --depth 1 https://github.com/starter-series/create-starterWrote 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/starter-series/create-starter/deploy-setup)<a href="https://agentmods.dev/skills/starter-series/create-starter/deploy-setup"><img src="https://agentmods.dev/badge/skills/starter-series/create-starter/deploy-setup/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/starter-series/create-starter/deploy-setup"><img src="https://agentmods.dev/badge/skills/starter-series/create-starter/deploy-setup.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.00061 | $0.02150 |
| Opus 5.5 | $0.00024 | $0.00860 |
| Sonnet 5.5 | $0.00012 | $0.00430 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
deploy-setup 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are walking a developer through the first deploy of a Starter Series project. The project has been scaffolded (via create-starter skill / CLI / MCP) and is on disk; this skill takes it from "scaffolded" to "first release published."
Prerequisites
- The project is already scaffolded and on disk. Verify by checking for
.github/workflows/cd*.ymlandpackage.json/pyproject.toml/Dockerfile. ghCLI is installed and authenticated (gh auth status). If not, instruct the user.- A GitHub repository exists for the project. If not, offer
gh repo create.
Workflow
Step 1: Detect the template
Read these files to identify which starter the project came from:
| Signal | Template |
|---|---|
package.json#mcpName starts with io.github. and package.json#main exists, no electron dep |
mcp-server (Node MCP) |
pyproject.toml references mcp package |
mcp-server-python |
package.json#dependencies.discord.js |
discord-bot |
package.json#dependencies.grammy |
telegram-bot |
manifest.json#manifest_version === 3 |
browser-extension |
package.json#engines.vscode |
vscode-extension |
package.json#dependencies.electron (or devDependencies.electron) |
electron-app |
package.json#dependencies.expo |
react-native |
wrangler.toml exists |
cloudflare-pages |
Dockerfile at root + no package.json |
docker-deploy |
package.json#publishConfig.access === "public" and no other signal |
npm-package |
Report the detected template name to the user.
Step 2: Inspect the CD workflow
Read .github/workflows/cd.yml (or cd-android.yml + cd-ios.yml for react-native, or cd-firefox.yml for browser-extension). Extract:
- The list of
secrets.Xreferenced inwith:/env:/if:blocks. These are the secrets that must be set. - Whether the workflow uses OIDC trusted publishing (look for
id-token: writeinpermissions:andnpm publish --provenance/pypa/gh-action-pypi-publishin steps). If yes, the publish step needs no token secret — only registry-side configuration (web UI). If no, a token secret is required.
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 · +2 lines ffec4e9814bd
- 1mo ago First seen · 143 lines · 61 tokens per session scan A e7e375148d53
deploy-setup is a skill published in the GitHub repository starter-series/create-starter (2 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 2,150 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
rhiza-remote
Check what CI on the origin says about this repo's open pull/merge requests, then diagnose and fix the red ones on their own branches. Reads the forge, reproduces locally, pushes fixes to the request's branch — never to the default branch.
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
gitlab-mcp-skill
Use this skill when working with the GitLab MCP server tools for merge requests, issues, repositories, pipelines, work items, variables, dependency proxy, vulnerabilities, webhooks, search, CI catalog, and related GitLab workflows.