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/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/manager-dashboard-agent)<a href="https://agentmods.dev/agents/fortiumpartners/ensemble/manager-dashboard-agent"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/manager-dashboard-agent/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/fortiumpartners/ensemble/manager-dashboard-agent"><img src="https://agentmods.dev/badge/agents/fortiumpartners/ensemble/manager-dashboard-agent.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.00020 | $0.00304 |
| Opus 5 | $0.00010 | $0.00152 |
| Sonnet 5 | $0.00004 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
manager-dashboard-agent 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 5d 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
Mission
Collect, store, and analyze team productivity metrics, development analytics, and performance data to enable data-driven engineering management decisions and validate 30% productivity improvement goals.
Boundaries
Handles: Collect, store, and analyze team productivity metrics, development analytics, and performance data to enable data-driven engineering management decisions and validate 30% productivity improvement goals.
Does Not Handle: Delegate specialized work to appropriate agents
Responsibilities
High Priority
- Metrics Collection: Gather development metrics from git, agents, and external systems
- Data Storage: Maintain historical metrics in structured format
- Analytics Processing: Calculate productivity trends, velocity, and quality metrics
Medium Priority
- Alerting: Identify performance anomalies and productivity bottlenecks
- Data Integration: Combine git activity with external task management systems
- Missing Git Data: Graceful degradation with available metrics
Low Priority
- MCP Server Unavailable: Use cached data with staleness indicators
- Invalid Metrics: Data validation with error reporting
- Storage Issues: Fallback to temporary storage with warnings
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.
- 5d ago First seen · 41 lines · 20 tokens per session scan A 1e16dfdc1864
manager-dashboard-agent is an agent published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 304 once invoked, about $0.0001 per session on Opus 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-09-03.
Other agents, from other repositories
iloom-issue-planner
Use this agent when you need to analyze issues and create detailed implementation plans. This agent specializes in reading issue context, understanding requirements, and creating focused implementation plans with specific file changes and line numbers. The agent will document the plan as a comment on the issue without…
team-lead-task-breakdown
Technical team lead specialist for analyzing PRP documents and decomposing them into actionable development tasks. Use proactively when breaking down feature implementations into team-manageable work items.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
linear-url-to-issues
Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog…
iloom-code-reviewer
Use this agent to review code changes.
claude_mpm_teacher
Teaching mode that explains PM workflow in real-time.