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 kok-o/contextos-agents --skill ci-cdgit clone --depth 1 https://github.com/kok-o/contextos-agentsWrote 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/kok-o/contextos-agents/ci-cd)<a href="https://agentmods.dev/skills/kok-o/contextos-agents/ci-cd"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/ci-cd/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/kok-o/contextos-agents/ci-cd"><img src="https://agentmods.dev/badge/skills/kok-o/contextos-agents/ci-cd.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.00035 | $0.00580 |
| Opus 5.5 | $0.00014 | $0.00232 |
| Sonnet 5.5 | $0.00007 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ci-cd 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 today.
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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD and Automation
Automate quality gates so no change reaches production without passing tests, lint, type checking, security scans, and build verification.
Core Philosophy
- Shift Left: Catch problems as early in the delivery lifecycle as possible. A defect caught during static analysis or linting takes seconds to fix; the same defect discovered in production takes hours and damages reliability.
- Faster is Safer: Small, frequent, automated releases drastically lower blast radius and risk compared to infrequent bulk deployments.
- Unskippable Gates Invariant: Never disable a failing rule or skip a test suite just to make a pipeline green. Fix the root cause in the code.
The Quality Gate Pipeline
Every Pull Request must successfully traverse these automated stages before merge approval:
Pull Request Opened
│
▼
1. Secret Scanning (prevent credential leaks before running untrusted steps)
│
▼
2. Lint & Formatting (eslint, prettier, markdownlint)
│
▼
3. Type Checking (tsc --noEmit, pyright, mypy)
│
▼
4. Unit Tests (vitest, jest, pytest with coverage thresholds)
│
▼
5. Production Build (bundling, tree-shaking, static generation)
│
▼
6. Integration Tests (API contracts, database migrations)
│
▼
7. Security Audit (npm audit, trivy, dependency vulnerability checks)
│
▼
8. Bundle Budget (bundle size checks against baseline thresholds)
│
▼
Merge Allowed
Hardened Pipeline Standards
- Least-Privilege Token Permissions:
Explicitly declare workflow and job permissions at the top of the workflow file. Default to read-only access:
permissions: contents: read - Deterministic Dependency Installation:
Always use frozen lockfiles (
npm ciinstead ofnpm install,uv sync --frozeninstead ofpip install). - Concurrency Cancellation:
Automatically cancel in-progress runs when a newer commit is pushed to the same Pull Request branch:
concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true - Action Pinning:
Reference trusted actions using verified release tags (e.g.
actions/checkout@v4) or full commit SHAs.
What ships with it
4 files 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.
- today First seen · 70 lines · 35 tokens per session scan A c00cc54401e1
ci-cd is a skill published in the GitHub repository kok-o/contextos-agents (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 580 once invoked, about $0.0001 per session on Opus 5.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-10-25.
Other skills, from other repositories
pin-github-actions
Migrates GitHub Actions workflows to use pinned commit SHAs instead of tags, resolves the latest release versions, flags major version jumps, and configures Dependabot with grouped updates. Use when user mentions pin actions, pinned versions, SHA pinning, GitHub Actions security, dependabot setup, supply-chain…
verify-pr-logs
Checks GitHub Actions CI logs on a pull request, diagnoses failures, and guides the agent to implement fixes. Use when user mentions CI failing, check PR logs, fix pipeline, GitHub Actions errors, workflow failures, build broken, tests failing on PR, or debug CI. Focuses on PR-scoped CI analysis only. For pinning…
Prompt Version Control Workflow
Sets up a prompt versioning system with naming conventions, diff tracking, A/B evaluation gates before promotion, and rollback triggers.
deploy-checklist
Pre-deploy and post-deploy checklist skill. Ensures env vars, migrations, CI, rollback plan, smoke tests, and monitoring are verified before and after every deployment.
kubestellar-console
Multi-cluster Kubernetes dashboard with AI-powered operations via MCP server and 10+ built-in agent skills.
github-master
Expert Git & GitHub: workflows, history recovery, pull requests, branch protection, and Actions CI/CD. Trigger keywords: git, GitHub, merge conflict, rebase, cherry-pick, reflog, bisect, force push, pull request, branch protection, GitHub Actions, CI/CD, release, conventional commits. Use for Git troubleshooting…