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 abinauv/business-consulting --skill change-managementgit clone --depth 1 https://github.com/abinauv/business-consultingWrote 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/abinauv/business-consulting/change-management)<a href="https://agentmods.dev/skills/abinauv/business-consulting/change-management"><img src="https://agentmods.dev/badge/skills/abinauv/business-consulting/change-management/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/abinauv/business-consulting/change-management"><img src="https://agentmods.dev/badge/skills/abinauv/business-consulting/change-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00049 | $0.06373 |
| Opus 5 | $0.00024 | $0.03187 |
| Sonnet 5 | $0.00010 | $0.01275 |
| Haiku 4.5 | $0.00005 | $0.00637 |
Grade A, and why
change-management 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 11d 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 — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Change Management Consulting Toolkit
You are an expert change management consultant. When the user describes an organizational change initiative, apply the frameworks, templates, and methodologies below to deliver actionable, executive-ready guidance. Tailor your analysis to the user's specific context — industry, organization size, culture, and change type.
1. Stakeholder Mapping and Influence Analysis
Power/Interest Grid
Classify every stakeholder into one of four quadrants based on their power (ability to influence the change outcome) and interest (degree to which they are affected by or care about the change).
HIGH POWER
|
Keep Satisfied | Manage Closely
(High Power, | (High Power,
Low Interest) | High Interest)
|
LOW INTEREST ——————————+———————————— HIGH INTEREST
|
Monitor | Keep Informed
(Low Power, | (Low Power,
Low Interest) | High Interest)
|
LOW POWER
Quadrant strategies:
| Quadrant | Strategy | Engagement Level | Tactics |
|---|---|---|---|
| Manage Closely (High Power, High Interest) | Active collaboration and co-creation | Weekly or more frequent touchpoints | Executive briefings, steering committee seats, 1:1 meetings, decision-making authority |
| Keep Satisfied (High Power, Low Interest) | Proactive updates, remove friction | Bi-weekly or monthly updates | Executive summaries, escalation-only meetings, respect their time |
| Keep Informed (Low Power, High Interest) | Transparent, frequent communication | Weekly communications | Town halls, newsletters, feedback channels, involvement in working groups |
| Monitor (Low Power, Low Interest) | Minimal but available information | As-needed or quarterly | Intranet updates, FAQs, open-door access |
What ships with it
3 files 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.
- 11d ago First seen · 550 lines · 49 tokens per session scan A fa048abf070a
change-management is a skill published in the GitHub repository abinauv/business-consulting (28 stars, last pushed 6mo ago), licensed MIT. It adds 49 tokens to every session and 6,373 once invoked, about $0.0002 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
markifact-overview
Reference — what Markifact is, what the MCP server exposes, and the discover→inspect→run pattern. Always loaded into the performance-marketer agent.
safe-write-operations
Reference — rules for safely executing write/destructive operations against ad accounts. Always loaded into the performance-marketer agent.
dev
Software development planning. Actions - spec (brainstorm product and tech specification), plan (turn the specs into a delivery plan - work packages, dependencies, effort in hours, milestones), feature (decompose specs into numbered feature documents), revise (update specs with new requirements), overview. Planning…
ws
Create and run workstations - permanent areas for routine, repeated work (independent of projects). Actions - new WS, new subWS, new area, new routine, run, from project, list, overview. Hierarchy depth (2 or 3 levels) is fixed at creation.
project
Create and manage the project structure - projects, sub-projects, and work packages (WPs). Actions - new project, new subproject, new WP, overview. Hierarchy depth (2 or 3 levels) is fixed at creation. All work happens in WPs; projects and sub-projects are pure structure.
axiom
AxiomCore front door - onboarding and module management. Actions - start (first-run setup, scaffolds the workspace), activate (M2-voice, M2-brand, M3, M4), deactivate , tier , language , status, overview. Run start in any new folder to set up the system.