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 fatihguner/foreman --skill team-culture-and-dynamicsgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/team-culture-and-dynamics)<a href="https://agentmods.dev/skills/fatihguner/foreman/team-culture-and-dynamics"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/team-culture-and-dynamics/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/fatihguner/foreman/team-culture-and-dynamics"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/team-culture-and-dynamics.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.00089 | $0.03808 |
| Opus 5 | $0.00044 | $0.01904 |
| Sonnet 5 | $0.00018 | $0.00762 |
| Haiku 4.5 | $0.00009 | $0.00381 |
Grade A, and why
team-culture-and-dynamics 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 6d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Team Culture and Dynamics
Every team has a temperature. The experienced leader reads it the way a pilot reads instruments -- not by staring at any single gauge but by registering the pattern across many: who speaks first in meetings and who waits; whether laughter is frequent or forced; how quickly Slack messages receive responses; whether disagreements happen in the room or in the corridor afterward; the tone of the last three emails from the same person. None of these signals is diagnostic on its own. Together, they constitute the emotional weather system of the team.
The theoretical architecture of team dynamics is well mapped. Tuckman describes the stages (forming, storming, norming, performing); Belbin catalogues the roles; Hackman identifies the enabling conditions. Those frameworks live in the frameworks directory and should be studied for their structural insight. This skill concerns itself with the question those frameworks do not fully answer: what does a leader actually do, day by day, to build and maintain a culture that converts individual talent into collective performance?
The Practice
Culture Is Manageable
Boris Groysberg, Jeremiah Lee, Jesse Price, and Yo-Jud Cheng's research contains a sentence that should unsettle every leader who treats culture as atmospheric and uncontrollable: "Culture can, in fact, be managed." The first step is awareness -- understanding how culture works, what values it embodies, and what behaviours it rewards and punishes. The second step is deliberate intervention. Most leaders produce detailed plans for strategy and execution but leave culture unmanaged, relegating it to HR as a secondary concern. The result: culture becomes an emergent property of accumulated defaults, not a designed system.
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.
- 6d ago First seen · 261 lines · 89 tokens per session scan A cf0a70e2fce7
team-culture-and-dynamics is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 89 tokens to every session and 3,808 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-09-06.
Other skills, from other repositories
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
design-team-culture
Use when a manager wants to intentionally shape the values, behaviors, and working patterns that define how their team operates — going beyond written norms to embed culture through rituals, stories, symbols, and leader modeling.
miro-workflow
Compose Miro boards from natural-language requests by combining tools from miro-mcp-server. Use when the user asks to set up a sprint board, retrospective, brainstorming session, user story map, kanban, or any structured Miro layout. Do NOT use for single-tool calls (create one sticky), questions about Miro the…
apply-cross-functional-leadership
Use when a manager needs to lead a project or initiative that depends on team members or stakeholders they do not formally manage — to build voluntary cooperation, alignment, and momentum across organizational boundaries through influence rather than authority.
apply-extreme-ownership
Use when leading a team and outcomes are falling short — to apply the principle that the leader owns every result, including failures caused by team members, as the non-negotiable foundation for improving performance and building trust.
design-team-norms
Use when a team is forming, after a significant membership change, or when a recurring dysfunction suggests the team lacks shared agreements on how to work together — to co-create explicit norms covering communication, decision-making, conflict, and accountability.