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 hackman-enabling-conditionsgit 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/hackman-enabling-conditions)<a href="https://agentmods.dev/skills/fatihguner/foreman/hackman-enabling-conditions"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/hackman-enabling-conditions.svg" alt="Measured on agentmods" 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.00099 | $0.03462 |
| Opus 5 | $0.00049 | $0.01731 |
| Sonnet 5 | $0.00020 | $0.00692 |
| Haiku 4.5 | $0.00010 | $0.00346 |
Grade A, and why
hackman-enabling-conditions 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 2d 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 — 224 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.
Hackman's Enabling Conditions for Team Effectiveness
Most team failures are not the team's fault. This is the central, uncomfortable conclusion of J. Richard Hackman's decades of research at Harvard on team performance -- research that studied airline cockpit crews, intelligence analysts, symphony orchestras, and corporate project teams. When a team underperforms, the reflexive organizational response is to blame the people: not talented enough, not motivated enough, not collaborative enough. Hackman's research redirects attention upward. In the majority of cases, the team fails because the conditions for success were never established. The soil was toxic; blaming the seeds for not growing is both lazy and wrong.
Hackman published his definitive framework in Leading Teams: Setting the Stage for Great Performances (2002), identifying five conditions that, when present, make team effectiveness probable -- and when absent, make it improbable regardless of how talented, committed, or well-intentioned the team members are. The framework shifts the leader's primary task from managing the team to designing the environment in which the team operates.
The Framework
Hackman's five enabling conditions form a hierarchy: each builds upon the previous. Condition 1 is foundational; without it, the others are meaningless. Condition 5 is the capstone, rarely present but transformative when it is.
Condition 1: Being a Real Team
The checklist question: Is this group actually a team, or merely a collection of individuals who report to the same manager?
A real team has three properties:
- Clear boundaries -- Everyone knows who is on the team and who is not. Ambiguous membership diffuses accountability and prevents cohesion.
- Interdependence -- Members need each other to accomplish the work. If everyone can complete their tasks independently, you have a workgroup, not a team -- and workgroups require different management.
- Stability -- Membership remains reasonably constant. Hackman's research shows that teams with frequent membership changes never reach high performance because they perpetually reset to Tuckman's Forming stage.
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.
- 2d ago First seen · 224 lines · 99 tokens per session scan A 17e626d29a20
hackman-enabling-conditions is a skill published in the GitHub repository fatihguner/foreman (47 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 3,462 once invoked, about $0.0005 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
apply-enabling-structure
Use when building or leading a team, organization, or system — to create the conditions, remove the obstacles, and design the structures that let people execute with high autonomy, rather than directing through control, because the best leaders are barely visible in their teams' day-to-day success.
manager-as-coach
A management approach in which managers help people do their best work instead of only supervising them. It focuses on using strengths, removing obstacles, setting clear expectations, giving recognition, and keeping teams small.
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.
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.
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.
apply-peter-principle-check
Use when designing a promotion process or deciding whether to promote someone based on strong current-role performance — explicitly test whether the skills that made them successful there are the same skills the next level requires, because promotion systems that reward current-role performance alone systematically…