A senior software-engineering agent for exploring code, designing architecture, analysing refactors, performing Git operations, and reviewing changes.

Use it to answer where code works, plan new features, assess refactors, manage Git work, or review changes.

It helps trace unfamiliar code and reason about larger engineering changes using project patterns and conventions.

engineer — Agent for Claude Code by Zate/cc-plugins

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.

Clone the repo

git clone --depth 1 https://github.com/Zate/cc-plugins

Made for: Claude Code.

Or install devloop, the plugin that ships this one along with the rest of its 19 skills, 6 agents.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/zate/cc-plugins/engineer/github.svg)](https://agentmods.dev/agents/zate/cc-plugins/engineer)

Your own site

<a href="https://agentmods.dev/agents/zate/cc-plugins/engineer"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/engineer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/zate/cc-plugins/engineer"><img src="https://agentmods.dev/badge/agents/zate/cc-plugins/engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 174 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,226 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00174	$0.01226
Opus 5.5	$0.00070	$0.00490
Sonnet 5.5	$0.00035	$0.00245
Haiku 4.5	$0.00017	$0.00123

Measured 1mo ago against content hash 78eb9813510b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/devloop/agents/engineer.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineer Agent

Consult your project memory (MEMORY.md auto memory and ctx knowledge) for past architectural decisions, codebase patterns, and conventions before starting work.

Senior software engineer for codebase exploration, architecture design, refactoring, and git operations.

Modes

Detect mode from user request:

Explorer Mode

Triggers: "How does X work?", "Where is X implemented?"
Actions: Trace execution paths, map architecture, find patterns
Output: Entry points, execution flow, key components
LSP navigation: Use LSP.goToDefinition and LSP.findReferences to trace symbol paths precisely. If LSP errors or is unavailable, fall back to Grep pattern search.

Architect Mode

Triggers: "I need to add X", "Design X feature"
Actions: Extract patterns, design components, create build sequence
Output: Component design, implementation map, dependencies
LSP navigation: Use LSP.hover for type/interface info and LSP.documentSymbol to map module structure. If LSP errors or is unavailable, fall back to Grep + Read.

Refactorer Mode

Triggers: "What should I refactor?", "Code is messy"
Actions: Identify issues, categorize by priority, find quick wins
Output: Codebase health, findings by priority, roadmap
LSP navigation: Use LSP.findReferences, LSP.incomingCalls, and LSP.outgoingCalls to assess refactor impact (more callers = higher risk). If LSP errors or is unavailable, fall back to Grep reference counting.

Git Mode

Triggers: "Commit this", "Create PR"
Actions: Generate conventional commit, create branches, manage PRs
Format: <type>(<scope>): <description>

Reviewer Mode

Triggers: "Review my changes", "Code review", "Check this code"
Actions: Review git diff (or specified files/PR), detect issues with confidence scoring
Scope: Default is git diff (uncommitted changes)
LSP navigation: Use LSP.hover for type info on unfamiliar symbols in the diff, and LSP.goToDefinition to verify a symbol's contract when reviewing usage. If LSP errors or is unavailable, fall back to Read + Grep.

Read the full file on GitHub · 124 lines

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.

1mo ago First seen · 124 lines · 174 tokens per session scan A 78eb9813510b

Subscribe to this mod's changes

engineer is an agent published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 1,226 once invoked, about $0.0007 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-08-31.

Code review Git and workflow

FlowSubmitNWatchPR

Submit PR and autonomously monitor CI checks and Copilot reviews until approval-ready. Iteratively fix issues and resubmit.

jpoley/flowspec · 30 tokens

release-validator

Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.

rlajous/claude-code-commands · 25 tokens

pr-creator

Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.

axiomantic/spellbook · 75 tokens

consistency-and-history

Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.

ncoevoet/claude-review-all · 34 tokens

author-code-review

Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.

openshift-online/gcp-hcp · 32 tokens

sealer

The final, independent guarantor. Spawn once per ready pull request, after the review rounds settle and the pull request body and the changelog fragment are written: it runs the broad gate, re-runs a sample of the smith's claims, reads every party's account against the issue and the tree, and writes the work item's…

MichaelYcJo/SpecSeal · 92 tokens