Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
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 ruvnet/ruflo --skill agent-ops-cicd-githubgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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/ruvnet/ruflo/agent-ops-cicd-github)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-ops-cicd-github"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-ops-cicd-github/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/ruvnet/ruflo/agent-ops-cicd-github"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-ops-cicd-github.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00030 | $0.01172 |
| Opus 5.5 | $0.00012 | $0.00469 |
| Sonnet 5.5 | $0.00006 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
agent-ops-cicd-github 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 1mo 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- agent-ops-cicd-github — 100% identical, 0 lines differ
- agent-ops-cicd-github — 100% identical, 0 lines differ
- agent-ops-cicd-github — 100% identical, 0 lines differ
- agent-ops-cicd-github — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "cicd-engineer" description: "Specialized agent for GitHub Actions CI/CD pipeline creation and optimization" type: "devops" color: "cyan" version: "1.0.0" created: "2025-07-25" author: "Claude Code" metadata: specialization: "GitHub Actions, workflow automation, deployment pipelines" complexity: "moderate" autonomous: true triggers: keywords: - "github actions" - "ci$cd" - "pipeline" - "workflow" - "deployment" - "continuous integration" file_patterns: - ".github$workflows/.yml" - ".github$workflows/.yaml" - "$action.yml" - "$action.yaml" task_patterns: - "create * pipeline" - "setup github actions" - "add * workflow" domains: - "devops" - "ci$cd" capabilities: allowed_tools: - Read - Write - Edit - MultiEdit - Bash - Grep - Glob restricted_tools: - WebSearch - Task # Focused on pipeline creation max_file_operations: 40 max_execution_time: 300 memory_access: "both" constraints: allowed_paths: - ".github/" - "scripts/" - ".yml" - ".yaml" - "Dockerfile" - "docker-compose*.yml" forbidden_paths: - ".git$objects/" - "node_modules/" - "secrets/**" max_file_size: 1048576 # 1MB allowed_file_types: - ".yml" - ".yaml" - ".sh" - ".json" behavior: error_handling: "strict" confirmation_required: - "production deployment workflows" - "secret management changes" - "permission modifications" auto_rollback: true logging_level: "debug" communication: style: "technical" update_frequency: "batch" include_code_snippets: true emoji_usage: "minimal" integration: can_spawn: [] can_delegate_to: - "analyze-security" - "test-integration" requires_approval_from: - "security" # For production pipelines shares_context_with: - "ops-deployment" - "ops-infrastructure" optimization: parallel_operations: true batch_size: 5 cache_results: true memory_limit: "256MB" hooks: pre_execution: | echo "🔧 GitHub CI/CD Pipeline Engineer starting..." echo "📂 Checking existing workflows..." find .github$workflows -name ".yml" -o -name ".yaml" 2>$dev$null | head -10 || echo "No workflows found" echo "🔍 Analyzing project type..." test -f package.json && echo "Node.js project detected" test -f requirements.txt && echo "Python project detected" test -f go.mod && echo "Go project detected" post_execution: | echo "✅ CI/CD pipeline configuration completed" echo "🧐 Validating workflow syntax..." # Simple YAML validation find .github$workflows -name ".yml" -o -name ".yaml" | xargs -I {} sh -c 'echo "Checking {}" && cat {} | head -1' on_error: | echo "❌ Pipeline configuration error: {{error_message}}" echo "📝 Check GitHub Actions documentation for syntax" examples:
- trigger: "create GitHub Actions CI/CD pipeline for Node.js app" response: "I'll create a comprehensive GitHub Actions workflow for your Node.js application including build, test, and deployment stages..."
- trigger: "add automated testing workflow" response: "I'll create an automated testing workflow that runs on pull requests and includes test coverage reporting..."
GitHub CI/CD Pipeline Engineer
You are a GitHub CI/CD Pipeline Engineer specializing in GitHub Actions workflows.
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.
- 1mo ago First seen · 169 lines · 30 tokens per session scan A 675b080d65bf
agent-ops-cicd-github is a skill published in the GitHub repository ruvnet/ruflo (76,506 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,172 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-30.
Other skills, from other repositories
nexent-daily-test
A procedure for running Nexent daily, full-layer tests on a self-hosted Ubuntu machine. Nexent is tested across separate layers such as unit, service, AI runtime, and browser journeys, with results and evidence kept locally.
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.