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 kotter-change-modelgit 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/kotter-change-model)<a href="https://agentmods.dev/skills/fatihguner/foreman/kotter-change-model"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/kotter-change-model/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/kotter-change-model"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/kotter-change-model.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.00090 | $0.03152 |
| Opus 5 | $0.00045 | $0.01576 |
| Sonnet 5 | $0.00018 | $0.00630 |
| Haiku 4.5 | $0.00009 | $0.00315 |
Grade A, and why
kotter-change-model 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 4d 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 — 188 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.
Kotter's 8-Step Change Model
Seventy percent of organizational change initiatives fail. That statistic, drawn from research spanning three decades and cited by John Kotter himself, should give pause to any founder contemplating a significant strategic shift. The failure rate is not declining. If anything, the acceleration of technological change has increased the number of transformation attempts without improving the success rate. Kotter, a Harvard Business School professor who spent his career studying why organizations resist change, distilled his findings into an eight-step model first published in his 1996 book Leading Change. The model remains the most widely taught change management framework in business schools worldwide -- not because it is novel, but because it is precise about where and why change efforts derail.
The Framework
The Eight Steps
Kotter's model is sequential by design. Skipping steps or reordering them is the primary cause of failure. Each step builds the foundation for the next.
Step 1 -- Create a Sense of Urgency Change begins only when enough people believe the status quo is more dangerous than the unknown. Kotter found that 50% of transformations fail at this first step because leaders underestimate the complacency embedded in successful organizations. The urgency must be authentic, not manufactured panic. Data-driven evidence of market shifts, competitive threats, or internal decay is more persuasive than executive rhetoric.
Step 2 -- Build a Guiding Coalition No single leader can drive change alone. Assemble a coalition of individuals with enough power, expertise, credibility, and leadership to sustain the effort. The coalition must include people from across the organization -- not just senior management. Kotter emphasizes that coalitions need leadership skills (setting direction, motivating) in addition to management skills (planning, budgeting, organizing).
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.
- 4d ago First seen · 188 lines · 90 tokens per session scan A 7c4ec229501e
kotter-change-model is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 3,152 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-change-leadership
Use when a manager's team is experiencing a significant organizational change — restructuring, strategy shift, leadership change, layoffs, or major process transition — and needs leadership that maintains team stability, preserves trust, and converts uncertainty into direction.
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…
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
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.
hatch3r-issue-workflow
Guides the 8-step agentic development workflow for issues/work items. Covers parsing issues, loading skills, reading specs, planning, implementing, testing, opening PRs/MRs, and addressing review. Use when working on any issue/work item or when the user mentions an issue number.