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 Vimalk0703/shipworthy --skill ci-cd-awarenessgit clone --depth 1 https://github.com/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/ci-cd-awareness)<a href="https://agentmods.dev/skills/vimalk0703/shipworthy/ci-cd-awareness"><img src="https://agentmods.dev/badge/skills/vimalk0703/shipworthy/ci-cd-awareness.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.00027 | $0.00442 |
| Opus 5 | $0.00014 | $0.00221 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
ci-cd-awareness 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.
What it actually says
CI/CD Awareness
Pipeline Structure
A well-designed pipeline follows this order:
1. Lint (fastest feedback)
- Run linters and formatters
- Fail fast on style violations
- Takes seconds, catches obvious issues
2. Type Check
tsc --noEmitor equivalent- Catches type errors before tests run
3. Test
- Unit tests first (fast)
- Integration tests second (slower)
- E2E tests last (slowest)
- Fail the pipeline if any test fails
4. Build
- Compile/bundle the application
- Verify the artifact is valid
5. Deploy
- Deploy to staging first
- Run smoke tests against staging
- Deploy to production with rollback capability
Environment Configuration
- Never hardcode environment-specific values
- Use environment variables for all configuration
- Maintain separate configs:
.env.development,.env.staging,.env.production - Validate all environment variables at startup (fail fast if missing)
Secrets in CI
- Use the CI platform's secret store (GitHub Secrets, etc.)
- Never echo secrets in logs
- Rotate secrets regularly
- Use minimal permissions (principle of least privilege)
Deployment Strategies
- Blue/green: run two environments, switch traffic
- Rolling: gradually replace old instances
- Canary: route small % of traffic to new version first
- Feature flags: deploy code behind flags, enable gradually
Rollback Plan
Every deployment must have a rollback strategy:
- How to detect a bad deployment (health checks, error rates)
- How to revert (previous container image, git revert, feature flag off)
- How long rollback takes
- Who is responsible for rollback decisions
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 · 65 lines · 27 tokens per session scan A b85fca72173d
ci-cd-awareness is a skill published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 442 once invoked, about $0.0001 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
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.
memstack-deployment-ci-cd-pipeline
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
ci-all
Full CI pipeline: run local tests, type check, push branch, and return the pipeline URL. The only command you need before opening a PR.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).