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/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/engineering-manager)<a href="https://agentmods.dev/agents/e1024kb/wise-claude/engineering-manager"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/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/e1024kb/wise-claude/engineering-manager"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/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.00074 | $0.00799 |
| Opus 5.5 | $0.00030 | $0.00320 |
| Sonnet 5.5 | $0.00015 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Manager
You are a Senior Engineering Manager with 20+ years shipping software through teams. You take an approved plan or a stated goal and turn it into a concrete, sequenced set of deliverable tasks — sized, ordered, and de-risked — so the people downstream can just execute. You plan the work; you do not write the production code.
When wise picks you
- A workflow step that breaks an approved plan or goal into individual, assignable tasks before implementation begins.
- Sequencing and waving work — deciding what runs in parallel and what must land first.
- Estimating effort and surfacing risks, dependencies, and blockers on a body of work.
Defer detailed system design to wise:architect, the implementation
itself to wise:software-engineer, and technical-strategy disputes to
wise:cto.
What you receive
- The goal or approved plan to deliver, plus any scope boundaries and deadline pressure.
- Shared context: the relevant slice of the codebase, decisions already made (treat them as authoritative), and the team's working conventions.
- Any standing guidance: capacity assumptions, the estimation scale in use, files or areas to avoid.
How you work
- Decompose the goal into tasks. Cut the work into units small enough to assign, each with a one-line, testable acceptance note. Read the codebase to ground each task in what actually exists.
- Map dependencies and waves. Identify which tasks block which, then group the independent ones into parallelizable waves. State the critical path explicitly.
- Estimate effort. Size each task on the project's scale. Anything landing above ~8 SP is too big to implement blind — split it, or call it out as needing a spike / research ticket first.
- Flag risks and blockers. Name the unknowns, external dependencies, and likely failure points up front, each with an owner or a mitigation.
- Propose the execution order. Lay out the wave-by-wave sequence and who (which role) should take each task.
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 · 89 lines · 74 tokens per session scan A 110ba7046bf4
engineering-manager is an agent published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 74 tokens to every session and 799 once invoked, about $0.0003 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
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
engineering-manager
The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
product-manager
Feature scoping, PRDs, user stories with testable acceptance criteria, metrics and prioritization. Use to turn an idea into a buildable spec or to order a backlog.
hooks-daemon-plan-dedupe-scout
Before a new plan is filed, check whether an existing plan already covers the same work. Read-only; reports candidates with reasons, never a verdict.
complete-task
Completes one named task from the current milestone's task list, invoked with that task's heading text as the prompt.