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 manishiitg/coding-agent-loop --skill ci-deployment-failure-triagegit clone --depth 1 https://github.com/manishiitg/coding-agent-loopWrote 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/manishiitg/coding-agent-loop/ci-deployment-failure-triage)<a href="https://agentmods.dev/skills/manishiitg/coding-agent-loop/ci-deployment-failure-triage"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/ci-deployment-failure-triage/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/manishiitg/coding-agent-loop/ci-deployment-failure-triage"><img src="https://agentmods.dev/badge/skills/manishiitg/coding-agent-loop/ci-deployment-failure-triage.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.00046 | $0.00727 |
| Opus 5.5 | $0.00018 | $0.00291 |
| Sonnet 5.5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
ci-deployment-failure-triage 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.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI and Deployment Failure Triage
Outcome
Create a repeatable workflow that receives CI/deployment failures, establishes exact change and environment identity, gathers evidence, classifies likely cause, performs policy-safe actions, and routes a concise finding to the right owner.
When to use
Use for failed, cancelled, stuck, or unhealthy build, test, release, and deployment events. Escalate active customer impact into the Incident Investigation playbook rather than treating it only as pipeline failure.
Discovery and user direction
Inspect the current workflow, goals, metrics, configuration, capabilities, stores, reports, and triggers before proposing changes. Summarize reusable design and gaps, then ask focused questions for unresolved customer choices such as scope, success, approvals, thresholds, ownership, and budgets. Record the answers as customer direction. Installation alone does not approve workflow changes or execution. Default to one small-team workflow; split only for incompatible access or lifecycle boundaries.
Required inputs
Resolve CI/CD providers, repositories/services/environments, event schemas, trigger and polling paths, pipeline/stage identity, log/artifact access, ownership, retry policy, failure taxonomy, severity/escalation rules, retention, notification destinations, and restricted-data policy.
Plan and AgentWorks tools
Use an authenticated webhook trigger for event-driven starts and a scripted step to validate/deduplicate input, fetch artifacts, redact evidence, and persist identity. Use a message sequence to compare hypotheses. Branch deterministically to safe rerun, owner routing, incident escalation, or hold. Use the Slack bot for threaded investigation and configured decisions.
Knowledge and persistence
Store failures, attempts, jobs/stages, changes, classifications, evidence pointers, known signatures, actions, and delivery receipts in durable tables/assets. Keep approved taxonomies and runbooks in KB context; promote a signature only after verification.
What ships with it
3 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.
- 1mo ago First seen · 52 lines · 46 tokens per session scan A 31d2da10d19f
ci-deployment-failure-triage is a skill published in the GitHub repository manishiitg/coding-agent-loop (13 stars, last pushed 19d ago), licensed MIT. It adds 46 tokens to every session and 727 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
ci-troubleshoot
Diagnose failed GitHub Actions runs for pi-agent-dashboard: the 11-file workflow taxonomy, affected-test selection, the release pipeline, known failure modes, and how to read gh run logs and retrigger jobs. Use when a CI run is red, a release is stuck, a workflow won't dispatch, or you need to know which workflow does…
goga-cell-go
Golang rules for implementing CODEMANIFEST contracts.
agency-devops-automator
Expert DevOps engineer specializing in infrastructure automation, CI/CD pipeline development, and cloud operations.
agency-mobile-release-engineer
Expert mobile release and distribution engineer for iOS and Android — code signing, provisioning, fastlane pipelines, App Store Connect and Play Console submission, phased rollouts, and crash-triaged release health.
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.