A collection of engineering team practices covering daily standups, code review, architecture decisions, incident response, and technical documentation. It can work with existing connected tools or on its own.

Use it to structure team meetings, review changes, record architecture choices, coordinate incident response, and create technical documents.

It helps organize recurring engineering work and gives teams consistent ways to review code, make technical decisions, handle incidents, and share knowledge.

engineering — Plugin by WARROOM-CEO

Install

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.

Claude Code

/plugin marketplace add WARROOM-CEO/CORE

agentmods

npx agentmods add plugins/warroom-ceo/core/engineering

Clone the repo

git clone --depth 1 https://github.com/WARROOM-CEO/CORE

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

engineering 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.

plugins/engineering/.claude-plugin/plugin.json · 10 lines

What it actually says

{
  "name": "engineering",
  "version": "1.2.0",
  "description": "ยกระดับการทำงานของทีมวิศวกรรมให้เป็นระบบและมีประสิทธิภาพ ครอบคลุมตั้งแต่ daily standups, code review, การตัดสินใจด้านสถาปัตยกรรม (architecture), การรับมือ incident ไปจนถึงการจัดทำเอกสารทางเทคนิค รองรับทั้งการเชื่อมต่อกับเครื่องมือที่ใช้อยู่เดิม หรือใช้งานแบบ standalone",
  "author": {
    "name": "WARROOM-CEO",
    "email": "[email protected]"
  }
}

Changes

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 · 10 lines scan A 7b2d8712152f

Subscribe to this mod's changes

engineering is a plugin published in the GitHub repository WARROOM-CEO/CORE (30 stars, last pushed 5mo 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-30.

Code review Planning Writing and docs

engineering

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

nextjs

nextjs

claude-plugins-official

knowledge-work-plugins

ecc

ecc