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.
/plugin marketplace add EngineerWithAI/engineerwith-agentsnpx agentmods add plugins/engineerwithai/engineerwith-agents/incident-responsegit clone --depth 1 https://github.com/EngineerWithAI/engineerwith-agentsWrote 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/engineerwithai/engineerwith-agents/incident-response)<a href="https://agentmods.dev/plugins/engineerwithai/engineerwith-agents/incident-response"><img src="https://agentmods.dev/badge/plugins/engineerwithai/engineerwith-agents/incident-response.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
incident-response 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.
What it actually says
{
"name": "incident-response",
"source": "./plugins/incident-response",
"description": "Production incident management, triage workflows, and automated incident resolution",
"version": "1.2.1",
"author": {
"name": "Mike Mayer",
"url": "https://github.com/EngineerWithAI"
},
"homepage": "https://github.com/EngineerWithAI/engineerwith-agents",
"repository": "https://github.com/EngineerWithAI/engineerwith-agents",
"license": "MIT",
"keywords": [
"incident-response",
"production",
"sre",
"troubleshooting"
],
"category": "operations",
"strict": false,
"commands": [
"./commands/incident-response.md",
"./commands/smart-fix.md"
],
"agents": [
"./agents/incident-responder.md",
"./agents/devops-troubleshooter.md"
],
"skills": [
"./skills/incident-runbook-templates",
"./skills/postmortem-writing",
"./skills/on-call-handoff-patterns"
]
}What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 123 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#incident-response 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.
- 2d ago First seen · 34 lines scan A 60cfaf9278f5
incident-response is a plugin published in the GitHub repository EngineerWithAI/engineerwith-agents (4 stars, last pushed 7mo 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-09-03.
Other plugins, from other repositories
systematic-debugging
Diagnose root causes with a four-phase debugging protocol. Use for ANY technical issue — test failures, production bugs, unexpected behavior, performance problems, build failures, or integration issues. ESPECIALLY when under time pressure, when "one quick fix" seems obvious, or when previous fix attempts have failed.…
datadog
Access Datadog logs, metrics, monitors, dashboards, SLOs, events, traces, and incidents.
agent-alchemy-dev-tools
Agent Alchemy Dev Tools — dev utilities, debugging, and workflow enhancements.
apple-craft
Apple 플랫폼 개발 스킬 모음 — 일반 구현/디버깅(apple-craft), 코드 리뷰(apple-review), 장기 대규모 구현 하네스(apple-harness, Designer 2-way split), App Store 배포 자동화(appstore-deploy), Xcode MCP 연동, xcodebuild+xcsift 빌드 폴백, Xcode 26 번들 문서 20개 + Swift 6.3 보강 + Concurrency Supplement(SE-0461/0466/0433, 차단형 동기화 정책) 내장, Pencil 디자인 통합.
debugging
Systematic debugging skills: root cause tracing, defense-in-depth validation, verification before completion.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.