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/sigistry/marketplaceWrote 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/plugins/sigistry/marketplace/ci-incident-medic)<a href="https://agentmods.dev/plugins/sigistry/marketplace/ci-incident-medic"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/ci-incident-medic/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/plugins/sigistry/marketplace/ci-incident-medic"><img src="https://agentmods.dev/badge/plugins/sigistry/marketplace/ci-incident-medic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ci-incident-medic 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 9d 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
{
"name": "ci-incident-medic",
"version": "1.0.0",
"description": "Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence.",
"author": {
"name": "Sigistry CI & Incident Medic",
"url": "https://github.com/Sigistry/marketplace/tree/main/plugins/ci-incident-medic"
},
"license": "MIT"
}
What it installs
The manifest is a name and a version. 4 skills, 5 commands, 3 agents travel with it, and installing the plugin installs all of them — 387 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill gha-failure-taxonomy A 83 tokens
- Skill incident-response A 78 tokens
- Skill dockerfile-smells B 76 tokens
- Skill k8s-manifest-validation B 84 tokens
- Command gha-triage A 14 tokens
- Command dockerfile-optimize A 15 tokens
- Command k8s-preflight A 14 tokens
- Command postmortem A 11 tokens
- Command workflow-review A 12 tokens
- Agent ci-failure-triager A 0 tokens
- Agent dockerfile-hardener A 0 tokens
- Agent postmortem-writer A 0 tokens
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.
- 9d ago First seen · 11 lines scan A f15feee06398
ci-incident-medic is a plugin published in the GitHub repository sigistry/marketplace (3 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
infrastructure
Infrastructure and DevOps specialists for AWS, GCP, Kubernetes, Docker, Terraform, GitHub Actions, GitLab CI, and security auditing.
handbook-glab
GitLab CLI (glab) expertise for managing merge requests, issues, CI/CD pipelines, and repositories from the command line.
platform-skills
Practical guidance for platform engineers across Claude, Codex, Cursor, and Copilot: Kubernetes (baseline, RBAC, workload hardening, debug), GitHub Actions (design, security, review, debug), Azure (Workload Identity, tagging, AKS, RBAC), OpenShift (SCC, Routes, GitOps, upgrades), Secrets (ESO, Sealed Secrets, rotation.
ci-failure-interpretation
Knowledge skill for interpreting CI failure logs from Shopware GitHub Actions workflows. Covers PHPUnit, PHPStan, ECS, ESLint, TypeScript, Stylelint, Prettier, Jest, Playwright, ludtwig, and Lighthouse.
sre-bot
SRE triage assistant for plain-English production health and Kubernetes questions in Slack. Read-only by default: the Kubernetes read connector exposes only read tools, and its credential cannot read Secrets or mutate resources. Grafana and Tempo connectors add observability reads. The one declared write verb rolls a…
portal-skills
Platform engineering and security skills: GitLab CI/CD + Helm chart generation for Kubernetes, data-driven pod rightsizing from Prometheus, a proactive secure-coding baseline, and a deep OWASP reference (Top 10:2025, LLM Top 10, Agentic AI).