whoop-mcp: Skill for Claude Code

.github/skills/ci-cd-and-automation/SKILL.md

ci-cd-and-automation is a skill for Claude Code, Codex from shashankswe2020-ux/whoop-mcp. It costs 45 tokens per session (2,719 once invoked), scanned A, a copy of ci-cd-and-automation, MIT.

A set of practices for automating software checks and releases. CI/CD means automatically checking code changes and moving approved changes through build, testing, and deployment stages.

In plain words
What is it for?
Use it to set up or change automated linting, type checking, tests, builds, pull-request checks, and deployment pipelines, or to diagnose failed pipeline runs.
Why use it?
It removes the need to run every quality check and deployment step manually. It helps catch problems before they reach users and makes releases smaller and easier to investigate.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is shashankswe2020-ux/whoop-mcp's own configuration. It tells Claude Code and Codex how to work on whoop-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything whoop-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to shashankswe2020-ux/whoop-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/shashankswe2020-ux/whoop-mcp/main/.github/skills/ci-cd-and-automation/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/shashankswe2020-ux/whoop-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ci-cd-and-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation/github.svg)](https://agentmods.dev/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation)
Your own site
<a href="https://agentmods.dev/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation/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.

agentmods 80×15 button for ci-cd-and-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation"><img src="https://agentmods.dev/badge/skills/shashankswe2020-ux/whoop-mcp/ci-cd-and-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,719 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.02719
Opus 5 $0.00023 $0.01359
Sonnet 5 $0.00009 $0.00544
Haiku 4.5 $0.00005 $0.00272

Measured 12d ago against content hash a6ed8ed56456, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ci-cd-and-automation 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 12d 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.

Origin

This is a copy

100% identical to ci-cd-and-automation — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/skills/ci-cd-and-automation/SKILL.md · 391 lines

How it starts

The opening of the file, as written. The whole thing — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CI/CD and Automation

Overview

Automate quality gates so that no change reaches production without passing tests, lint, type checking, and build. CI/CD is the enforcement mechanism for every other skill — it catches what humans and agents miss, and it does so consistently on every single change.

Shift Left: Catch problems as early in the pipeline as possible. A bug caught in linting costs minutes; the same bug caught in production costs hours. Move checks upstream — static analysis before tests, tests before staging, staging before production.

Faster is Safer: Smaller batches and more frequent releases reduce risk, not increase it. A deployment with 3 changes is easier to debug than one with 30. Frequent releases build confidence in the release process itself.

When to Use

  • Setting up a new project's CI pipeline
  • Adding or modifying automated checks
  • Configuring deployment pipelines
  • When a change should trigger automated verification
  • Debugging CI failures

The Quality Gate Pipeline

Every change goes through these gates before merge:

Pull Request Opened
    │
    ▼
┌─────────────────┐
│   LINT CHECK     │  eslint, prettier
│   ↓ pass         │
│   TYPE CHECK     │  tsc --noEmit
│   ↓ pass         │
│   UNIT TESTS     │  jest/vitest
│   ↓ pass         │
│   BUILD          │  npm run build
│   ↓ pass         │
│   INTEGRATION    │  API/DB tests
│   ↓ pass         │
│   E2E (optional) │  Playwright/Cypress
│   ↓ pass         │
│   SECURITY AUDIT │  npm audit
│   ↓ pass         │
│   BUNDLE SIZE    │  bundlesize check
└─────────────────┘
    │
    ▼
  Ready for review

No gate can be skipped. If lint fails, fix lint — don't disable the rule. If a test fails, fix the code — don't skip the test.

GitHub Actions Configuration

Basic CI Pipeline

# .github/workflows/ci.yml
name: CI

on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  quality:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: actions/setup-node@v4
        with:
          node-version: '22'
          cache: 'npm'

      - name: Install dependencies
        run: npm ci

      - name: Lint
        run: npm run lint

      - name: Type check
        run: npx tsc --noEmit

      - name: Test
        run: npm test -- --coverage

      - name: Build
        run: npm run build

      - name: Security audit
        run: npm audit --audit-level=high

Read the full file on GitHub · 391 lines

Changes

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.

  1. 12d ago First seen · 391 lines · 45 tokens per session scan A a6ed8ed56456

Subscribe to this mod's changes

ci-cd-and-automation is a skill published in the GitHub repository shashankswe2020-ux/whoop-mcp (153 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,719 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ci-cd-and-automation, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

afrexai-performance-engineering

Complete performance engineering system — profiling, optimization, load testing, capacity planning, and performance culture. Use when diagnosing slow applications, optimizing code/queries/infrastructure, load testing before launch, planning capacity, or building performance into CI/CD. Covers Node.js, Python, Go…

LeoYeAI/openclaw-master-skills · 71 tokens

flutter-mcp-toolkit-repo-maintainer

Maintain mcpflutter releases, CHANGELOG, version pins, docs, and CI. Use when cutting a release, editing CHANGELOG.md, bumping VERSION, running release-please, sync-skills, check-contracts, or updating install/docs for npx skills and flutter-mcp-toolkit init.

Arenukvern/mcp_flutter · 71 tokens

woodpecker-ci

Operate Woodpecker CI from installation through production troubleshooting: configure servers and agents, connect Forgejo/Gitea or another forge, write and validate pipelines, manage secrets and plugins, use Docker or Kubernetes backends, run the CLI, and diagnose failed builds. Use when setting up, administering, or…

magnus919/agent-skills · 87 tokens

platform-engineering

Use this skill when building or operating internal developer platforms: infrastructure as code, CI/CD, container orchestration, service networking, secrets, and observability. Do not use it to define release process, promotion, rollout, or rollback policy; use release-engineering for that delivery model.

magnus919/agent-skills · 61 tokens

github-runner

Deploy, manage, and troubleshoot self-hosted GitHub Actions runners. Covers systemd service, Docker containers, Kubernetes (Actions Runner Controller), and the Scale Set Client. Use when setting up a CI runner, debugging registration failures, designing autoscaling, or hardening runner security. Do not use this skill…

magnus919/agent-skills · 76 tokens

release-engineering

Design, automate, and operate end-to-end software releases: release process models and pipelines (trunk-based development, CD stages, release trains), progressive delivery and feature flags, versioning and artifact management (SemVer, conventional commits, changelogs, SBOM/provenance), readiness and quality gates…

magnus919/agent-skills · 158 tokens