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/christopherlouet/claude-baseWrote 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/agents/christopherlouet/claude-base/ops-ci)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/ops-ci"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-ci/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/agents/christopherlouet/claude-base/ops-ci"><img src="https://agentmods.dev/badge/agents/christopherlouet/claude-base/ops-ci.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.00025 | $0.00438 |
| Opus 5.5 | $0.00010 | $0.00175 |
| Sonnet 5.5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
ops-ci 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 14d 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
Agent OPS-CI
Configuration of complete CI/CD pipelines.
Workflow
- CI Pipeline: lint + typecheck -> tests (with DB services) -> build (Docker multi-stage)
- CD Pipeline: deploy staging (develop) -> deploy production (main) with environments
- Dependabot/Renovate: automatic dependency updates
- Branch protection: require CI pass, require review
Supported platforms
- GitHub Actions: YAML workflows, services, cache actions, GHCR
- GitLab CI: stages, .node-cache, services, artifacts, environments
Best practices
- Cache dependencies for speed
- Parallel jobs (lint + test in parallel)
- Fail fast for quick feedback
- Separate environments (staging/production)
- Secrets via GitHub Secrets / CI variables
Expected output
- Complete CI workflow (lint, test, build)
- CD workflow with environments (staging, production)
- Dependabot/Renovate config
- Branch protection rules
Guidelines
- NEVER hardcode secrets in workflows
- IMPORTANT: Always cache dependencies
- YOU MUST use pinned versions for actions (actions/checkout@v4)
- IMPORTANT: Deploy production with manual approval or environment protection
- NEVER use plaintext passwords in CI configurations
Think hard about pipeline security and speed.
See also
GitHub's own github-actions-hardening skill (github/awesome-copilot, MIT, pin 143a3d97) goes deeper on workflow security: token permissions, pinning actions by SHA, untrusted input in run:, pull_request_target. It does not generate pipelines and does not cover GitLab — authoring stays here.
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.
- 14d ago Changed · +4 lines 040c57f52672
- 1mo ago First seen · 49 lines · 25 tokens per session scan A beb4d1f3f9ad
ops-ci is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 438 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-08-31.
Other agents, from other repositories
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
game-developer
Expert game developer for Unity, Unreal Engine, and Godot game development.