Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/6529-Collections/6529seize-frontendnpx agentmods add skills/6529-collections/6529seize-frontend/deploy-6529Wrote 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/6529-collections/6529seize-frontend/deploy-6529)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/deploy-6529"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/deploy-6529/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/6529-collections/6529seize-frontend/deploy-6529"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/deploy-6529.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.00051 | $0.02139 |
| Opus 5 | $0.00026 | $0.01069 |
| Sonnet 5 | $0.00010 | $0.00428 |
| Haiku 4.5 | $0.00005 | $0.00214 |
Grade A, and why
deploy-6529 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 yesterday.
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy 6529
Prepare
- Read the user's requested phase and current PR/CI state. Complete the applicable review and validation requirements before release work. Continue through the authorized phase without asking for the same permission again; staging authorization alone does not authorize production.
- Determine the affected repositories and backend services from the diff and
backend
src/config/deploy-services.json, including real dependency order and allowed environments. Deploy only required units. Follow each repo's6529wrapper rules for package commands. - For a new staging or direct production release intent that includes frontend, establish the exact release inputs: requester, target, database-change status, PR branches, and full PR head SHAs. Follow Coordinator release recording before any merge or deployment mutation.
- Fetch the destination branch and merge without discarding other developers' work. If it moves, fetch and recompute; resolve conflicts in the development branch where appropriate. Never force-push shared branches.
- Use GitHub Actions run visibility to avoid conflicting deployments. Wait for another developer's conflicting work to finish; do not cancel it. Existing workflow concurrency is repository-scoped, so coordinate coupled BE/FE work explicitly.
Coordinator release recording
Run this step once per new staging release intent or new direct production release intent that includes frontend. For a coupled release, submit one request from the frontend repository containing all relevant frontend and backend parts. Backend-only work is outside this integration.
Do not create another request for status checks, monitoring, merge-only work, retries, resumes, recovery, production continuation, or promotion of an already recorded release. Reuse the existing outcome and evidence on continuation, including after a returned failure; do not resubmit to repair the record during the release.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +90 lines 328c7fc868ae
- 6d ago Changed · -71 lines · -19 tokens per session 3835c5d32a88
- 10d ago First seen · 166 lines · 70 tokens per session scan A b8cb5421d26c
deploy-6529 is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 2,139 once invoked, about $0.0003 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
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
releasepr
Adopt, configure, run, or troubleshoot compozy/releasepr in a consuming repository, including Actions, beta/stable/legacy plans, notes, dry-runs, and publication. Excludes pr-release internals and general versioning advice.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…