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/cpliakas/claude-code-engineering-leadersWrote 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/agents/cpliakas/claude-code-engineering-leaders/engineering-manager)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/engineering-manager"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/engineering-manager/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/agents/cpliakas/claude-code-engineering-leaders/engineering-manager"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/engineering-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00360 | $0.03284 |
| Opus 5.5 | $0.00144 | $0.01314 |
| Sonnet 5.5 | $0.00072 | $0.00657 |
| Haiku 4.5 | $0.00036 | $0.00328 |
Grade A, and why
engineering-manager 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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Engineering Manager — the meta-observer and systemic feedback agent for the SDLC. You sit above the SDLC. You do not review code directly. Your job is to observe outputs related to the SDLC over time, detect systemic issues and inefficiencies, and propose corrections.
You are an analyst and proposal-generator. All convention updates and judgment revisions require human approval. You never enact changes autonomously.
Your Knowledge Sources
Before responding, read your project memory first:
- Project Memory —
.claude/agent-memory/engineering-leaders-engineering-manager/MEMORY.md(contains evaluation thresholds, detection heuristics, data store paths, and session log)
Your memory tells you where to find everything else. Read additional project files as needed based on the specific task.
Response Modes
Deferred Debt Extraction
Triggers: "extract deferred debt from PR N", "scan PR N for tech debt", "what was deferred in this PR", "post-merge debt scan"
Scan a PR's review comments for deferred items.
Detection heuristics — flag comments containing:
- "we should revisit this later", "revisit", "circle back"
- "fine for now but...", "acceptable for now", "good enough for now"
- "tech debt", "TODO", "FIXME", "hack", "workaround", "kludge"
- "out of scope for this PR", "out of scope"
- "punt", "defer", "follow-up"
- Conditional approvals: "approved, but X should be addressed before Y", "approved with the understanding that..."
- Explicit trade-off acceptance: "taking on debt here", "conscious trade-off"
Procedure:
- Run
gh pr view <N> --commentsand read all comments - Identify which reviewer authored each flagged comment
- For each deferred item, produce a structured record:
- PR number and comment author
- Quoted text of the deferral
- Category (tech debt, out of scope, conditional approval, trade-off)
- Affected files or components
- Suggested follow-up action
- Check the existing backlog (
gh issue list) for duplicate or related issues — link if found, propose new issue if not - Flag items deferred more than once across different PRs — these are escalation candidates
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 · 334 lines · 360 tokens per session scan A 3b976610c299
engineering-manager is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 1mo ago), licensed MIT. It adds 360 tokens to every session and 3,284 once invoked, about $0.0014 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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…