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 lewin-leadership-stylesgit 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/lewin-leadership-styles)<a href="https://agentmods.dev/skills/fatihguner/foreman/lewin-leadership-styles"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/lewin-leadership-styles/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/lewin-leadership-styles"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/lewin-leadership-styles.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.00078 | $0.02769 |
| Opus 5 | $0.00039 | $0.01385 |
| Sonnet 5 | $0.00016 | $0.00554 |
| Haiku 4.5 | $0.00008 | $0.00277 |
Grade A, and why
lewin-leadership-styles 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.
How it starts
The opening of the file, as written. The whole thing — 176 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.
Lewin's Leadership Styles
Imagine three identical teams of ten people, each given the same project, the same deadline, and the same resources. The only variable is the leader. Team A's leader makes every decision, assigns every task, and monitors every output. Team B's leader sets the vision, then asks the team how they want to get there. Team C's leader says "figure it out" and retreats to their office. Kurt Lewin ran essentially this experiment in 1939 with groups of children -- and the results mapped with uncomfortable precision onto dynamics that play out in every startup, corporation, and nonprofit today. The autocratic group produced more output but lower quality and collapsed when the leader left. The democratic group produced slightly less volume but far higher quality and sustained performance independently. The laissez-faire group produced the least, with the most frustration and the worst interpersonal dynamics.
Three styles. Three radically different organizational outcomes. Lewin's framework remains the foundation upon which all subsequent leadership theory was built.
The Framework
Lewin identified three primary leadership styles along a spectrum of control. The framework is descriptive (leaders tend toward one style) and prescriptive (certain contexts reward certain styles).
The Three Styles Compared
| Dimension | Autocratic | Democratic | Laissez-Faire |
|---|---|---|---|
| Decision authority | Leader decides alone | Leader facilitates group input, then decides or delegates | Leader abdicates decision-making |
| Communication flow | Top-down, directive | Bidirectional, consultative | Minimal, reactive |
| Team autonomy | Low; tasks are assigned with specific instructions | Moderate; team participates in planning and execution choices | High in theory, chaotic in practice |
| Speed of decisions | Fast | Moderate | Slow or absent |
| Innovation | Low; risk-aversion dominates | High; diverse perspectives surface | Variable; depends entirely on team capability |
| Team morale | Low long-term; resentment builds | High; ownership breeds engagement | Low; absence of guidance feels like abandonment |
| Quality of output | Variable; depends on leader's expertise | Consistently high; collective intelligence corrects errors | Typically low; no quality standards enforced |
| Scalability | Poor; bottleneck at the leader | Strong; distributed decision-making scales | Unpredictable; works only with exceptional self-managing teams |
| Leader absence impact | Severe; work stops or quality collapses | Minimal; team continues autonomously | None; the leader was already functionally absent |
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 · 176 lines · 78 tokens per session scan A 42edcc55123d
lewin-leadership-styles is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 6d ago), licensed MIT. It adds 78 tokens to every session and 2,769 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
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.
apply-five-commander-virtues
Use when assessing, developing, or hiring for leadership capability — to evaluate a leader against the five virtues that Sun Tzu identifies as determinants of strategic success and diagnose which virtue deficits are causing organisational or competitive failures.
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
summarize-activity
Summarize engineering activity in classroomio/classroomio between two dates — merged PRs, still-open PRs opened in that window, and their demo videos — into a markdown report. Use when the user asks what shipped, what happened, or for a summary/recap/digest of engineering work over a date range.