Agent Claude Code
Meta-reviewer and loop-breaker. Governs both phases (pre-PR and on-PR review), enforces the gates and cycle limits, and decides continue/approve/escalate so agents never loop. Risk-aware and multi-service aware.
Agent Claude Code
Implements the planned change on a feature branch and addresses PR review comments. Handles single-repo and coordinated multi-service changes; keeps changes minimal and contract-safe.
Agent Claude Code
Turns a feature request into a concrete spec and execution plan. Identifies which repo(s)/microservices are affected (one or many), the cross-service contract changes, the ordered task breakdown with dependencies, and the risks. Read-only — produces the plan the team executes.
Agent Claude Code
Read-only adversarial reviewer. Pre-PR it returns a verdict for the arbiter; on an open PR it posts true line-anchored INLINE comments via the git-host API, written in the PR's own language. Scores risk and checks cross-service compatibility. Never edits code.
Agent Claude Code
Runs and writes tests — the green-build gate. Covers per-repo unit/integration tests and the cross-service seam when a feature spans services.
Skill Claude CodeCodex
When writing code against an external library, framework, SDK, or API, look up its CURRENT documentation with the context7 MCP tools instead of relying on memory. Use whenever you import/call a third-party package or hit an unfamiliar or fast-moving API.
Skill Claude CodeCodex
Before telling the user a coding task is done, actually verify it — build, run the relevant tests/linter, and confirm the change does what was asked with no regressions. Use whenever you are about to claim a change is finished, fixed, or working.
Agent Claude Code
Handles Telegram Business messages on behalf of the owner with read-only knowledge retrieval.
Agent Claude Code
Handles LO messages on behalf of the owner with read-only knowledge retrieval.
Skill Claude CodeCodex
Answer questions about the owner's services and domain using the approved DuckBug knowledge base through configured MCP tools.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: