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 agentmods add skills/hoavdc/codexkit/codexkit-change-management-plannpx skills add hoavdc/CodexKit --skill codexkit-change-management-plangit clone --depth 1 https://github.com/hoavdc/CodexKitWhat 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 | $0.00058 | $0.01345 |
| Opus 5 | $0.00029 | $0.00673 |
| Sonnet 5 | $0.00012 | $0.00269 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
codexkit-change-management-plan 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Management Plan
When to Use
- When rolling out a new system or tool to an organization
- When restructuring teams or processes
- When policy changes affect daily workflows
- When previous change initiatives failed due to poor adoption
Procedure
Step 1 — Change Definition
| Element | Description |
|---|---|
| What is changing? | [Current state → Future state] |
| Why? | [Business driver / burning platform] |
| Who is affected? | [Roles, teams, departments] |
| When? | [Timeline with milestones] |
| Scale | Minor (team) / Moderate (department) / Major (organization) |
Step 2 — ADKAR Assessment
Score each element 1–5 for the affected population:
| ADKAR Element | Score | Gap? | Intervention |
|---|---|---|---|
| Awareness — know why change is needed | 3 | Yes | Leadership comms |
| Desire — want to participate | 2 | Yes | WIIFM messaging |
| Knowledge — know how to change | 1 | Yes | Training program |
| Ability — can demonstrate new skills | 1 | Yes | Practice + coaching |
| Reinforcement — sustain the change | TBD | — | Post-launch support |
Focus on the first gap — you can't build Desire without Awareness.
Step 3 — Stakeholder Map
| Stakeholder | Impact | Influence | Current Stance | Target Stance | Strategy |
|---|---|---|---|---|---|
| CTO | High | High | Champion | Champion | Activate as sponsor |
| Team leads | High | Medium | Neutral | Supportive | 1:1 briefings |
| End users | High | Low | Resistant | Accepting | Demo + early wins |
Step 4 — Communication Plan
| Date | Audience | Channel | Message | Sender | Goal |
|---|---|---|---|---|---|
| Week 1 | All staff | Town hall | Why we're changing | CEO | Awareness |
| Week 2 | Team leads | Workshop | What it means for your team | PM | Desire |
| Week 3 | Users | Email + Video | How it works | Project team | Knowledge |
| Ongoing | All | Slack channel | Tips, wins, FAQ | Champions | Reinforcement |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 157 lines · 58 tokens per session scan A b27d9562089f
codexkit-change-management-plan is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 1,345 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-planner
Agent skill for planner - invoke with $agent-planner.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
maintain
Maintain the slopus/happy open source project. Triage issues, draft closing comments, find duplicates, check if bugs are fixed on main, and engage with community contributors. NEVER posts comments or closes issues without showing exact text and getting approval first.
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.