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 daddia/claude-for-strategy --skill resistance-diagnosisgit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/resistance-diagnosis)<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.
<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>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.00059 | $0.01209 |
| Opus 5.5 | $0.00024 | $0.00484 |
| Sonnet 5.5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
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 1mo 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 — 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-logwhen 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
-
Read practice profile — resistance taxonomy, escalation thresholds, sponsor model.
-
Document observed resistance — behaviors (skipping training, shadow IT, public criticism, quiet non-use), not labels ("toxic," "blocker").
-
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.
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.
- 1mo ago First seen · 124 lines · 59 tokens per session scan A 968c84fad0ef
resistance-diagnosis is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,209 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
review
Run the full pre-merge panel: parallel audit and lens reviewers over a diff, consolidated into one severity-ranked verdict.
tdd
Test-driven development, from unit to end-to-end tests. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration or end-to-end tests (Playwright, Cypress). Don't use to backfill tests on existing code (/refactor) or diagnose an unknown bug (/debug).
visual-review
Two visual modes — render a PR diff as an HTML page with each hunk annotated by principle, or check a UI change in a real browser (screenshots, console, network). Use for a visual/HTML diff report, "check the UI", or "screenshot before/after". Don't use for text-only feedback (/code-review), unit tests (/tdd), or full…
to-pr
Gate, push, and open a GitHub pull request on the repo's PR template, then watch CI.
to-tickets
Slice a spec or a ticket into tracer-bullet tickets with blocking edges, published through the repo's tracker: .specs/tickets/ .md by default.
debate
Settle a go/no-go on one risky change against an alternative through an advocate, a skeptic, and a neutral investigator.