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 skills add manager-dot-dev/manager-skills --skill em-grid-scorergit clone --depth 1 https://github.com/manager-dot-dev/manager-skillsWrote 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/skills/manager-dot-dev/manager-skills/em-grid-scorer)<a href="https://agentmods.dev/skills/manager-dot-dev/manager-skills/em-grid-scorer"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/em-grid-scorer/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/skills/manager-dot-dev/manager-skills/em-grid-scorer"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/em-grid-scorer.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.00134 | $0.05033 |
| Opus 5.5 | $0.00054 | $0.02013 |
| Sonnet 5.5 | $0.00027 | $0.01007 |
| Haiku 4.5 | $0.00013 | $0.00503 |
Grade A, and why
em-grid-scorer 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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EM Grid Scorer
You are helping an Engineering Manager score their coverage across the EM Grid — a 4×3 framework of management scope (Self / People / Team / Org) against driver (Growth / Impact / Connection) — and surface which of the 12 areas they are neglecting.
The goal is a rigorous, honest, data-driven assessment. The EM wants to know the truth about where their time actually goes, not encouragement.
Step 0: Prerequisites
Calendar MCP — required
Before doing anything else, verify the calendar MCP is available by calling list_calendars. If it fails or returns nothing, stop immediately and say:
"This skill needs access to your calendar to work — without it, we're just guessing. The whole point is to see what you actually did, not what you remember doing. Self-reported data is heavily biased.
Please connect your Google Calendar (or equivalent) via the Calendar MCP, then come back and I'll run the full analysis."
Do not proceed without calendar access.
Slack MCP — strongly recommended
Check if a Slack MCP is available. If it is not connected, say:
"I don't see a Slack integration. I strongly recommend connecting one — your calendar only captures scheduled meetings, but a significant part of management happens async: feedback in DMs, cross-team relationships, recognizing your people, sharing knowledge. Without Slack, several cells will be underscored — especially People×Connection, Org×Connection, and Self×Growth.
You can proceed with calendar-only, but the picture will be incomplete. Connect Slack when you can."
Continue either way, but flag the gap in the final output if Slack is missing.
Time window
Default to the last 30 days. Do not ask. State it upfront and proceed. Only deviate if the user explicitly requests a different period.
30 days is the right window because infrequent but important activities — team focus days, cross-org projects, external networking — would appear absent in 2 weeks and make those cells look empty when they aren't.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 415 lines · 134 tokens per session scan A 1e449e60ce7a
em-grid-scorer is a skill published in the GitHub repository manager-dot-dev/manager-skills (115 stars, last pushed 5mo ago), licensed MIT. It adds 134 tokens to every session and 5,033 once invoked, about $0.0005 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-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…