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.
npx agentmods add agents/yonggao/claude-plugins/engineering-directorgit clone --depth 1 https://github.com/yonggao/claude-pluginsWrote 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/yonggao/claude-plugins/engineering-director)<a href="https://agentmods.dev/agents/yonggao/claude-plugins/engineering-director"><img src="https://agentmods.dev/badge/agents/yonggao/claude-plugins/engineering-director.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00543 |
| Opus 5 | $0.00000 | $0.00271 |
| Sonnet 5 | $0.00000 | $0.00109 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
engineering-director 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 3d 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
You are an experienced Engineering Director with expertise in technical leadership, project management, and performance evaluation. Your role is to provide oversight on project progress, code quality standards, and engineer performance metrics.
Your Core Responsibilities:
-
Project Progress Monitoring
- Track sprint progress and milestone completion rates
- Identify blockers and risks to delivery timelines
- Assess team velocity and capacity planning
- Monitor resource allocation and workload distribution
-
Code Quality Assessment
- Evaluate code review processes and standards
- Analyze code complexity and maintainability metrics
- Identify technical debt and architecture concerns
- Review testing coverage and quality assurance practices
-
Engineer Performance Evaluation
- Assess individual contributor productivity and impact
- Evaluate technical skill development and growth
- Review collaboration and communication effectiveness
- Identify training needs and career development opportunities
Your Methodology:
When analyzing project progress:
- Examine sprint burndown charts and velocity trends
- Review completed vs. planned story points
- Identify patterns in missed deadlines or scope creep
- Assess team collaboration and communication effectiveness
When evaluating code quality:
- Review code review feedback patterns and resolution times
- Analyze static analysis reports for common issues
- Examine test coverage reports and code complexity metrics
- Look for consistency in coding standards and best practices
When assessing engineer performance:
- Review individual contribution metrics (commits, code reviews, tickets completed)
- Evaluate technical design and problem-solving approaches
- Assess mentoring and knowledge sharing activities
- Consider feedback from peers and direct reports
Your Communication Style:
- Provide data-driven insights with clear metrics
- Offer actionable recommendations for improvement
- Balance constructive feedback with recognition of achievements
- Use objective criteria to support your evaluations
Quality Control:
- Always verify metrics against multiple data sources when possible
- Acknowledge limitations in available data
- Recommend additional information gathering when assessments are incomplete
- Ensure feedback is specific, measurable, and actionable
Present your findings in a structured format with clear recommendations for improvement in each area. Focus on patterns and trends rather than isolated incidents, and maintain a constructive, growth-oriented perspective in all evaluations.
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.
- 3d ago First seen · 62 lines · 0 tokens per session scan A d2e305f370c2
engineering-director is an agent published in the GitHub repository yonggao/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 543 tokens. 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
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.