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.
git clone --depth 1 https://github.com/contentstack/contentstack-agent-skillsWrote 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/rules/contentstack/contentstack-agent-skills/20-launch-trigger-and-monitor-launch-deployments)<a href="https://agentmods.dev/rules/contentstack/contentstack-agent-skills/20-launch-trigger-and-monitor-launch-deployments"><img src="https://agentmods.dev/badge/rules/contentstack/contentstack-agent-skills/20-launch-trigger-and-monitor-launch-deployments.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.1 | $0.01197 | $0.01197 |
| Opus 5 | $0.00598 | $0.00598 |
| Sonnet 5 | $0.00239 | $0.00239 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
20-launch-trigger-and-monitor-launch-deployments 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 8d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger and Monitor Launch Deployments
Description
Trigger a Launch deployment for a specific environment, then poll its status until completion. If the deployment fails or is cancelled, fetch the deployment log and diagnose likely causes with next-step recommendations.
When to Use
Use when you need to automate Launch deployments for a known project and environment, monitor progress, and surface failure diagnostics. This is appropriate for CI/CD or operator workflows that need a deterministic deploy status check and log-based troubleshooting.
User Problem
Users need a reliable way to start a deployment in Launch, track it to completion, and quickly understand why it failed if it does. The skill should reduce manual polling and make deployment failures actionable.
Success Criteria
Deployment is triggered against the intended project and environment. Status is polled at a fixed interval until a terminal state is reached. The process exits non-zero on failed or cancelled deployments. If the deployment fails, the deployment log is retrieved and summarized with likely causes and next steps. Production targets are validated and require explicit confirmation before deployment.
Expected Inputs
- project_uid
- environment_uid
- Optional deployment payload or build reference
- Confirmation for production deployment when applicable
- Any available context about the app, branch, or build source
Expected Outputs
- Deployment UID and initial trigger response
- Current status updates during polling
- Terminal status and exit code
- Deployment log summary when failures occur
- Recommended next steps and probable root cause
Example User Requests
- Trigger a deployment for project abc123 in environment prod456 and watch it until it finishes.
- Deploy the latest build to staging and tell me if it fails.
- If the deployment fails, check the logs and explain what went wrong.
- Poll a Launch deployment every 10 seconds and exit non-zero on failure.
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.
- 8d ago First seen · 152 lines · 1,197 tokens per session scan A 718a65baadc2
20-launch-trigger-and-monitor-launch-deployments is a cursor rule published in the GitHub repository contentstack/contentstack-agent-skills (5 stars, last pushed 21d ago), licensed MIT. It adds 1,197 tokens to every session, about $0.0060 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 cursor rules, from other repositories
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.