run-team-health-check

run-team-health-check is a skill for Claude Code from jeffreytse/grimoire-core. It costs 51 tokens per session (2,081 once invoked), scanned A, original, MIT.

A periodic assessment of team health across areas such as trust, clarity, workload, collaboration, and inclusion.

In plain words
What is it for?
Use it to assess how the team is functioning, identify weak areas, and decide which issues need attention.
Why use it?
It surfaces team problems through structured feedback before they become conflicts, missed goals, or people leaving.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Use it to assess how the team is functioning, identify weak areas, and decide which issues need attention.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/run-team-health-check
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill run-team-health-check
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

Wrote 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.

agentmods badge for run-team-health-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-team-health-check/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/run-team-health-check)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-team-health-check"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-team-health-check/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.

agentmods 80×15 button for run-team-health-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/run-team-health-check"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/run-team-health-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,081 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00051 $0.02081
Opus 5.5 $0.00020 $0.00832
Sonnet 5.5 $0.00010 $0.00416
Haiku 4.5 $0.00005 $0.00208

Measured 1mo ago against content hash 0e4733bac7ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

run-team-health-check 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.

skills/business/leadership/skills/run-team-health-check/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run Team Health Check

Administer a periodic structured assessment of team health across key dimensions — trust, clarity, workload, collaboration, and inclusion — to surface problems early through data rather than waiting for attrition, conflict, or missed goals to reveal them.

Why This Is Best Practice

Adopted by: Spotify's Squad Health Check Model (2014) is the most widely replicated team health assessment in the technology industry, adopted by Zalando, ING, Autodesk, and hundreds of engineering organizations; Google's Project Aristotle (2016) established five team effectiveness dimensions that became the basis for Google's own team health assessment tools; Lencioni's "Five Dysfunctions" assessment has been administered to hundreds of thousands of teams globally and is one of the most widely used team diagnostics in business; the US Army's Command Climate Survey is the military equivalent — mandatory at all echelons above company level Impact: Spotify's internal data on health check adoption found that teams running quarterly health checks identified and resolved team dysfunction 60% faster than teams relying on manager observation alone (Kniberg retrospective, 2015); Google Project Aristotle found that psychological safety — one health dimension — explained more variance in team performance than any other single factor; McKinsey's Organizational Health Index (45,000+ organizations assessed) found that companies in the top quartile of organizational health generate 3× total return to shareholders compared to bottom-quartile companies Why best: Manager observation is a lagging indicator — by the time a manager observes a team health problem, it has usually been present for weeks or months; team members who are experiencing a problem are often reluctant to raise it to their manager (especially if the manager is part of the problem); a structured, anonymous health check creates a direct channel for team health data that bypasses the social dynamics that suppress candid manager feedback

Read the full file on GitHub · 122 lines

Changes

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.

  1. 1mo ago First seen · 122 lines · 51 tokens per session scan A 0e4733bac7ea

Subscribe to this mod's changes

run-team-health-check is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 2,081 once invoked, about $0.0002 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-09-03.