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 agentmods add commands/christopherlouet/claude-base/ops-cigit 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/commands/christopherlouet/claude-base/ops-ci)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-ci"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-ci.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 | $0.00000 | $0.00297 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
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 yesterday.
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 Agent
Configure CI/CD pipelines (GitHub Actions, GitLab CI, etc.).
Request context
$ARGUMENTS
Objective
Generate complete CI/CD pipelines adapted to the project's technical stack, with lint, test, build, security, and deployment steps.
Workflow
- Analyze the technical stack and existing configuration
- Identify the needs (lint, typecheck, test, build, security, e2e, deploy)
- Generate the appropriate GitHub Actions or GitLab CI workflows
- Configure caching and parallelization for performance
- Add PR checks and release workflows
- Document the secrets to configure
- Verify that permissions are minimal
Expected output
- Workflows: ci.yml, pr.yml, deploy.yml, release.yml
- Secrets to configure with instructions
- Checklist for setup (workflows, secrets, branch protection, dependabot)
Related agents
| Agent | Usage |
|---|---|
/ops:ops-docker |
Build Docker images |
/ops:ops-release |
Automate releases |
/ops:ops-secrets-management |
CI secrets management |
IMPORTANT: Test the pipeline on a test branch before merging to main.
YOU MUST use secrets for all credentials - never in clear text.
NEVER grant excessive permissions to the GITHUB_TOKEN.
Think hard about the steps that are truly necessary - a fast pipeline is a used pipeline.
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.
- yesterday First seen · 46 lines · 0 tokens per session scan A 8451ca5a61fe
ops-ci is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 297 tokens. 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-09-03.
Other commands, from other repositories
workflow-automation
Integrate AI swarms with GitHub Actions to create intelligent, self-organizing CI/CD pipelines that adapt to your codebase.
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...
workflow-manager
Process automation with TodoWrite planning and Task execution.
intent
Press-release intent lifecycle — status, quoted-text create, the implement-readiness gate, and the human planning interview that turns a draft into a planned, specced intent.
command-template.claude
Command "command-template.claude" from Enovatr-Labs/SpecRoute, covering what this command does, implementation, inline shell commands the slash command runs, output and when to use.
refine
Refine vague legal queries into structured prompts through Socratic dialogue, with workflow recommendations and multi-lingual terminology guidance.