resistance-diagnosis

resistance-diagnosis is a skill for Claude Code from daddia/claude-for-strategy. It costs 59 tokens per session (1,209 once invoked), scanned A, original, MIT.

A method for diagnosing why people resist a workplace change, separating visible behavior from possible underlying causes. It considers factors such as perceived loss, lack of confidence, habit, and competing interests.

In plain words
What is it for?
Use it to analyze adoption problems, stalled change, and people-side blockers before deciding on communication, training, sponsorship, or escalation.
Why use it?
It helps avoid treating all pushback as the same problem or blaming individuals. It gives leaders response options while marking conclusions as hypotheses when evidence is limited.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md.

Part of the change-management plugin — 5 skills shipped together

Good fit Use it to analyze adoption problems, stalled change, and people-side blockers before deciding on communication, training, sponsorship, or escalation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/daddia/claude-for-strategy/resistance-diagnosis
Install

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.

Any agent
npx skills add daddia/claude-for-strategy --skill resistance-diagnosis
Clone the repo
git clone --depth 1 https://github.com/daddia/claude-for-strategy

Made for: Claude Code.

Or install change-management, the plugin that ships this one along with the rest of its 5 skills.

Wrote 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.

agentmods badge for resistance-diagnosis

README.md
[![agentmods](https://agentmods.dev/badge/skills/daddia/claude-for-strategy/resistance-diagnosis/github.svg)](https://agentmods.dev/skills/daddia/claude-for-strategy/resistance-diagnosis)
Your own site
<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/resistance-diagnosis"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/resistance-diagnosis/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.

agentmods 80×15 button for resistance-diagnosis

Your own site · 80×15
<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/resistance-diagnosis"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/resistance-diagnosis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,209 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01209
Opus 5 $0.00030 $0.00605
Sonnet 5 $0.00012 $0.00242
Haiku 4.5 $0.00006 $0.00121

Measured 11d ago against content hash 968c84fad0ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

resistance-diagnosis 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.

change-management/skills/resistance-diagnosis/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Resistance Diagnosis

When to use

Diagnose observed resistance — separate symptoms from root causes; offer response options across sponsor, comms, training, and structural levers without mandating a single fix.

What this skill does not do

  • Does not log governance decisions — route continue/escalate calls to /pmo:decision-log when installed.
  • Does not label people as blockers — describes behaviors and incentives, not character.
  • Does not recommend punitive action by default — escalation is an option, not the default response.

Preconditions

Input If missing
Observed resistance (quotes, behaviors, metrics) Ask for specific examples
Stakeholder segment affected Ask who; link to map if available
Practice profile resistance taxonomy Use loss/competence/habit/politics defaults

Provisional mode

With anecdote only: hypothesize root causes; flag [review] — need corroboration before major escalation.

Trust spine

  • Confidence bands (hypothesis-driven-analysis):
    • High: Multiple independent observations; root cause tied to named loss or incentive.
    • Medium: Single source or manager report; hypotheses labeled.
    • Low: Vague "they don't like it" — ask for behaviors before prescribing.
  • Failure modes:
    • Analytical rigor: Distinguish active sabotage from passive workarounds from capacity overload.
    • Strategic advice vs. support: Present response options; leadership owns escalation and trade-offs.

Workflow

  1. Read practice profile — resistance taxonomy, escalation thresholds, sponsor model.

  2. Document observed resistance — behaviors (skipping training, shadow IT, public criticism, quiet non-use), not labels ("toxic," "blocker").

  3. Classify root cause (may be multiple):

    • Loss — status, autonomy, relationships, job security.
    • Competence — fear of failing at new process; insufficient skill.
    • Habit — old way is faster under pressure; no muscle memory yet.
    • Politics — incentive misalignment; another leader's priority conflicts.
    • Capacity — change stacked on BAU with no time budget — often misread as attitude.

Read the full file on GitHub · 124 lines

Changes

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.

  1. 11d ago First seen · 124 lines · 59 tokens per session scan A 968c84fad0ef

Subscribe to this mod's changes

resistance-diagnosis is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,209 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-31.

Related

Other skills, from other repositories

swarmclaw

AI agent runtime and multi-agent orchestration platform. Teaches agents how to use SwarmClaw's 6 primitive tools, persistent memory, dreaming, delegation, connectors, credentials, and the skill system. Use when an agent is running on SwarmClaw and needs to understand the platform's capabilities.

swarmclawai/swarmclaw · 67 tokens

spec-herdr-review

Run visible multi-agent spec reviews in Herdr through interactive agent CLIs such as Claude, Codex, Copilot/GLM, or Grok/Composer. Supports two modes — a spec review (the design, before implementation) and an implementation review (the implemented diff vs the spec, after the calling model has built it). Ask for…

stewartcelani/skills · 88 tokens

gpmc

Read-only Active Directory Group Policy inventory via LDAP — list GPOs, show OU/site links (enabled/disabled/enforced), find unlinked GPOs, search by name, and gpresult for the current user. Use when the user asks about GPOs, Group Policy, GPMC, linked vs unlinked policies, RSoP, what applies to this user, or runs…

stewartcelani/skills · 115 tokens

grok-session

Find and inspect local Grok CLI conversations by session GUID, title, phrase, or recent activity. Use when the user runs /grok-session, asks what Grok work they have been doing lately, says a Grok conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named session, or wants to continue…

stewartcelani/skills · 85 tokens

claude-session

Find and inspect local Claude Code conversations by session GUID, title, phrase, or recent activity. Use when the user runs /claude-session, asks what Claude Code work they have been doing lately, says a Claude Code conversation died, ran out of context, crashed, or exhausted usage, wants to resume a named…

stewartcelani/skills · 80 tokens

codex-session

Find and inspect local Codex task conversations, including by session GUID, title, recent activity, or a phrase from the conversation. Use when the user runs /codex-session, says a prior Codex conversation died or ran out of context, wants to resume a named task, asks what a local Codex task did, or wants to continue…

stewartcelani/skills · 81 tokens