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 Primadetaautomation/primadata-marketplace --skill deployment-workflowsgit clone --depth 1 https://github.com/Primadetaautomation/primadata-marketplaceWrote 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/primadetaautomation/primadata-marketplace/deployment-workflows)<a href="https://agentmods.dev/skills/primadetaautomation/primadata-marketplace/deployment-workflows"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/deployment-workflows/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/primadetaautomation/primadata-marketplace/deployment-workflows"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/deployment-workflows.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.00022 | $0.03252 |
| Opus 5 | $0.00011 | $0.01626 |
| Sonnet 5 | $0.00004 | $0.00650 |
| Haiku 4.5 | $0.00002 | $0.00325 |
Grade A, and why
deployment-workflows 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 9d 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 https://myapp.com/health How it starts
The opening of the file, as written. The whole thing — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Workflows Skill
Overview
This skill provides comprehensive deployment strategies including CI/CD pipelines, zero-downtime deployments, and infrastructure as code patterns for production-ready applications.
When to Use This Skill
- Setting up deployment pipelines
- Configuring production infrastructure
- Implementing zero-downtime deployments
- Disaster recovery procedures
- Monitoring and alerting setup
Pre-Deployment Checklist (Level 1 - Always Loaded)
🚀 Production Readiness Checklist
Before deploying to production:
- All tests passing (unit, integration, E2E)
- Test coverage ≥ 80%
- Security scan passed (no critical vulnerabilities)
- No hardcoded secrets
- Environment variables documented
- Database migrations tested
- Monitoring configured
- Logging implemented
- Error tracking setup (Sentry/equivalent)
- Rate limiting enabled
- HTTPS enforced
- Backup strategy defined
- Rollback plan documented
- Performance tested under load
- Documentation updated
Zero-Downtime Deployment Strategy
Blue-Green Deployment
# Deploy new version (green) alongside old version (blue)
# Switch traffic once green is verified healthy
steps:
1. Deploy new version (green) to separate infrastructure
2. Run smoke tests on green environment
3. Switch 10% of traffic to green (canary)
4. Monitor metrics for 10 minutes
5. If metrics healthy, switch 100% traffic to green
6. Keep blue running for 1 hour (quick rollback if needed)
7. Decommission blue environment
Rolling Deployment
# Update instances one at a time
steps:
1. Remove instance from load balancer
2. Deploy new version to instance
3. Run health checks
4. Add instance back to load balancer
5. Repeat for next instance
6. Monitor error rates between updates
Database Migration Strategy
// Safe migration pattern (zero-downtime)
// Step 1: Add new column (deploy v1.1)
// Migration: Add column with nullable constraint
ALTER TABLE users ADD COLUMN email_verified BOOLEAN;
// Application code: Write to both old and new schema
async function updateUser(userId: string, data: any) {
// Write to new column if provided
if (data.emailVerified !== undefined) {
await db.query(
'UPDATE users SET email_verified = $1 WHERE id = $2',
[data.emailVerified, userId]
);
}
}
// Step 2: Backfill data (background job)
async function backfillEmailVerified() {
// Migrate existing data in batches
await db.query(`
UPDATE users
SET email_verified = false
WHERE email_verified IS NULL
`);
}
// Step 3: Make column non-nullable (deploy v1.2)
ALTER TABLE users ALTER COLUMN email_verified SET NOT NULL;
// Step 4: Remove old code paths (deploy v1.3)
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.
- 9d ago First seen · 536 lines · 22 tokens per session scan A 9a027d0169f1
deployment-workflows is a skill published in the GitHub repository Primadetaautomation/primadata-marketplace (5 stars, last pushed 9mo ago), licensed MIT. It adds 22 tokens to every session and 3,252 once invoked, about $0.0001 per session on Opus 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
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-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
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.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.