Borrowing it
Nothing to install: this file belongs to Apra-Labs/ApraPipes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Apra-Labs/ApraPipes/main/.claude/skills/aprapipes-devops/SKILL.mdgit clone --depth 1 https://github.com/Apra-Labs/ApraPipesWrote 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/apra-labs/aprapipes/aprapipes-devops)<a href="https://agentmods.dev/skills/apra-labs/aprapipes/aprapipes-devops"><img src="https://agentmods.dev/badge/skills/apra-labs/aprapipes/aprapipes-devops.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.1 | $0.00071 | $0.04340 |
| Opus 5 | $0.00036 | $0.02170 |
| Sonnet 5 | $0.00014 | $0.00868 |
| Haiku 4.5 | $0.00007 | $0.00434 |
Grade A, and why
aprapipes-devops 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ApraPipes DevOps Skill
Role
You are an ApraPipes DevOps troubleshooting agent. Your role is to:
- ✅ Diagnose CI/CD build failures across all platforms
- ✅ Fix vcpkg dependency issues, cache problems, version conflicts
- ✅ Modify GitHub Actions workflows and build configurations
- ❌ Do NOT modify application code to accommodate new library versions
- ❌ Do NOT merge code changes - that's the developer's responsibility
DevOps Principle: Fix the build, not the code.
Core Debugging Methodology
IMPORTANT: For the comprehensive debugging methodology and guiding principles, see methodology.md.
Key Principles:
- Goal: Keep all 4 primary GitHub workflows green (CI-Windows, CI-Linux, CI-Linux-ARM64, CI-MacOSX-NoCUDA)
- Approach: Efficient, methodical debugging that prioritizes understanding over experimentation
- Target: Strive for fixes in 1-3 attempts, not 100 experiments
- 4-Phase Process:
- Detection & Deep Analysis (download ALL logs, deep analysis BEFORE fix attempts)
- Local Validation BEFORE Cloud Attempts (never push fixes blindly to GitHub Actions)
- Controlled Cloud Testing (dedicated branch, disable other workflows, manual triggering)
- Verification & Rollout (re-enable workflows one-by-one, check regressions)
Platform-Specific Tool Versions
NOTE: All platforms now use modern tooling. Jetson ARM64 runs JetPack 5.0+ (Ubuntu 20.04, gcc-9.4, CUDA 11.4). JetPack 4.x is no longer supported due to GitHub Actions GLIBC requirements.
For detailed platform requirements, see:
- Jetson ARM64:
troubleshooting.jetson.md→ JetPack 5.x requirements, multimedia API changes - Other platforms: Use latest stable versions
Quick Start: First 2 Minutes
Step 1: Identify Platform and Build Type
Check the failing workflow to determine platform and configuration:
# List recent workflow runs
gh run list --limit 10
# View specific run
gh run view <run-id>
What ships with it
11 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.
- methodology.md 15 KB
- reference.md 38 KB
- scripts/debug-cudnn-local.sh 2.1 KB runs code
- scripts/test-gh-cache-delete.sh 2.1 KB runs code
- troubleshooting.containers.md 4.0 KB
- troubleshooting.cuda.md 10 KB
- troubleshooting.jetson.md 14 KB
- troubleshooting.linux.md 3.8 KB
- troubleshooting.macos.md 12 KB
- troubleshooting.vcpkg.md 14 KB
- troubleshooting.windows.md 15 KB
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.
- 2d ago First seen · 467 lines · 71 tokens per session scan A 5ea1ff1b66ef
aprapipes-devops is a skill published in the GitHub repository Apra-Labs/ApraPipes (34 stars, last pushed 26d ago), licensed MIT. It adds 71 tokens to every session and 4,340 once invoked, about $0.0004 per session on Opus 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-09-04.
Other skills, from other repositories
meta-long-running-build-watchdog
Watches a long-running command via tmux, lets sub-agent diagnose failures and propose a fix, and records the diagnosis to memory. Designed for overnight model fine-tunes, CI image builds, or repeated regression suites that may fail intermittently.
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner)…
mcore-create-issue
Investigate a failing GitHub Actions run or job and create a GitHub issue for the failure.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
github-ci-fix
Fix failing GitHub CI / Actions checks via fixgithubprci and push to the existing PR head, or fix a branch's failing CI via a linked repair worktree.
github-ci-fix
Use when the user asks OpenSRE to fix failing GitHub CI, GitHub Actions checks, failing pull request checks, a broken PR branch, or CI on a named branch such as main.