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 organisational-culturegit 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/organisational-culture)<a href="https://agentmods.dev/skills/fatihguner/foreman/organisational-culture"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/organisational-culture/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/organisational-culture"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/organisational-culture.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.03131 |
| Opus 5 | $0.00039 | $0.01566 |
| Sonnet 5 | $0.00016 | $0.00626 |
| Haiku 4.5 | $0.00008 | $0.00313 |
Grade A, and why
organisational-culture 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 — 201 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.
Organisational Culture
What you see in an organisation -- the open-plan offices, the Friday beers, the branded hoodies -- is the tip of the iceberg. Roughly ten percent of culture is visible. The remaining ninety percent sits submerged: the unspoken beliefs, the unstated power hierarchies, the assumptions so deeply embedded that no one thinks to question them. Edgar Schein, the MIT professor who spent decades dissecting how organisations actually work, argued that most culture-change initiatives fail because they redecorate the tip while ignoring the mass below the waterline. The iceberg metaphor is not merely illustrative; it is diagnostic. Misread which level of culture you are dealing with, and your intervention will achieve nothing -- or worse, provoke the immune response that organisations mount against superficial change.
Schein's framework identifies three distinct layers, each progressively harder to observe and exponentially harder to alter. Understanding these layers is not an academic exercise. For founders, it is the difference between building a company that scales with coherence and one that fractures under the weight of its own contradictions.
The Framework
Layer 1: Artifacts (The Visible Surface)
Artifacts are everything you can see, hear, and touch when you walk into an organisation. Office layout. Dress code. Meeting rituals. The language people use in Slack channels. The way decisions get announced. These are tangible, immediately observable -- and profoundly misleading if interpreted without context.
A startup with a foosball table and no dress code might appear egalitarian. The reality could be a cult of personality where the CEO's whims override all process. Artifacts are symptoms, not diagnoses.
Common artifacts include:
- Physical environment and workspace design
- Published values and mission statements
- Rituals, ceremonies, and recurring events
- Stories and legends told about the company's origins
- Organisational charts and reporting structures
- Technology choices and communication tools
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 · 201 lines · 78 tokens per session scan A bfcbb1bde6f7
organisational-culture is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 78 tokens to every session and 3,131 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-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.
dumbest-in-the-room
A leadership practice for building a team whose members have deeper expertise than the leader in their areas. The leader focuses more on asking questions, sharing information, and giving people authority to decide.
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…
fly
Fly one thought to its destination across concurrent agents, on whatever the project and harness already have. Lands only when the user has accounted for every detail, never on an agent's say-so.
plan-to-issues
A tool that turns an agreed work plan into linked GitHub issues, with one larger parent issue and smaller task issues beneath it.