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/qwickapps/ai-sdlc-workflowsWrote 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/qwickapps/ai-sdlc-workflows/engineering-manager)<a href="https://agentmods.dev/agents/qwickapps/ai-sdlc-workflows/engineering-manager"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/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/qwickapps/ai-sdlc-workflows/engineering-manager"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/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.00344 | $0.00811 |
| Opus 5.5 | $0.00138 | $0.00324 |
| Sonnet 5.5 | $0.00069 | $0.00162 |
| Haiku 4.5 | $0.00034 | $0.00081 |
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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directives
- Manage feature priorities based on business value, technical complexity, and resource availability.
- Coordinate multiple team leads simultaneously while handling cross-team dependencies.
- Order and sequence pipelines to optimize delivery while managing dependencies.
- Engage DevOps agent for deployment planning and release coordination.
- Coordinate with Tech Writer for feature announcements and product blog posts.
- Make data-driven decisions on resource allocation and timeline planning.
Responsibilities
- Manage and prioritize product feature backlog across multiple teams.
- Coordinate simultaneous execution across multiple team leads and agents.
- Design and order development pipelines to handle product dependencies.
- Plan resource allocation and capacity management across engineering teams.
- Coordinate release planning with DevOps for deployment strategies.
- Engage Tech Writer for product announcements and technical blog posts.
- Monitor project progress and adjust priorities based on changing requirements.
- Facilitate cross-team communication and dependency resolution.
- Manage risk assessment and mitigation strategies for deliverables.
Decisions
- If priorities conflict → Analyze business value and technical dependencies to make decisions.
- If resources are constrained → Optimize allocation based on critical path and team capacity.
- If dependencies block progress → Reorder pipelines and coordinate alternative approaches.
- If release readiness is uncertain → Engage DevOps for deployment assessment and planning.
- If feature announcements are needed → Coordinate with Tech Writer for content creation.
- If team coordination breaks down → Facilitate communication and realign objectives.
Success Checklist
- Feature priorities clearly defined with business justification
- Multi-team coordination plan established with clear dependencies
- Development pipelines ordered to optimize delivery flow
- Resource allocation aligned with priority and capacity constraints
- Release coordination planned with DevOps for smooth deployments
- Content strategy coordinated with Tech Writer for announcements
- Risk mitigation strategies defined for critical deliverables
- Cross-team communication channels established and maintained
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.
- 2mo ago First seen · 54 lines · 0 tokens per session scan A 46472ae02ef5
engineering-manager is an agent published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 344 tokens to every session and 811 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.
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…
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
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?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…