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 techwolf-ai/ai-first-toolkit --skill team-healthgit clone --depth 1 https://github.com/techwolf-ai/ai-first-toolkitWrote 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/techwolf-ai/ai-first-toolkit/team-health)<a href="https://agentmods.dev/skills/techwolf-ai/ai-first-toolkit/team-health"><img src="https://agentmods.dev/badge/skills/techwolf-ai/ai-first-toolkit/team-health/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/techwolf-ai/ai-first-toolkit/team-health"><img src="https://agentmods.dev/badge/skills/techwolf-ai/ai-first-toolkit/team-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01538 |
| Opus 5 | $0.00036 | $0.00769 |
| Sonnet 5 | $0.00014 | $0.00308 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
team-health 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 9d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Health Check
Two lenses, always. "Development" asks: is this person growing and performing? "Wellbeing" asks: is this person thriving, connected, and energised? Great managers hold both.
A periodic overview of team dynamics, engagement signals, wellbeing, and development trajectory across all direct reports.
When to Use
- Weekly or biweekly team health review
- Before calibration or planning meetings
- When the manager says "how's my team doing?", "team health check", "anyone I should check in with?"
- When preparing for skip-level conversations
Instructions
If any MCP connector is unavailable, follow the connector unavailability protocol in references/operating-principles.md.
1. Load Team Context
Read from manager-context/:
manager-profile.md: full list of direct reportsteam/: individual profiles with goals, projects, last review datessources.md: channels and data locations per team member
If context is missing, note it and work with available sources.
2. Scan Per Team Member
For each direct report, gather data from the last 14 days (or since last health check):
Activity & Engagement (Slack):
- Message volume in team/project channels (relative to their baseline if known)
- Types of messages: asking questions, answering questions, sharing updates, celebrating, flagging issues
- Channels they're active in
- Any public wins or recognition received
- Any public frustration or repeated blockers
1:1 Cadence (Calendar):
- When was their last 1:1 with the manager?
- Were recent 1:1s kept or cancelled?
- Are they overdue for a 1:1?
Development Goals (Notion/Drive):
- Last time their goals were updated
- Any progress notes or self-assessments
- Are there development areas with no recent activity?
Workload Signals (Calendar + Slack):
- Meeting load (heavy/normal/light for their role)
- Are they in channels/meetings outside their usual scope? (scope expansion, could be good or concerning)
Wellbeing & Connection Signals (Slack + Calendar):
- Energy & wellbeing: late-night messages, weekend activity, signs of overwork
- Connection: are they participating in non-work channels (#random, social threads, team celebrations)?
- Celebration: have they been recognised or praised recently? Have they celebrated others?
- Tone: are their messages upbeat, neutral, or showing signs of frustration/fatigue? (use as a soft signal only, never diagnose)
- Fun & enjoyment: any signs of passion, enthusiasm, or joy in their work (shipping excitement, sharing wins, volunteering for things)?
What ships with it
2 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.
- 9d ago First seen · 139 lines · 72 tokens per session scan A 7391ba7ee72b
team-health is a skill published in the GitHub repository techwolf-ai/ai-first-toolkit (99 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,538 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.