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 fzfclee/consulting-skills --skill force-field-analysisgit clone --depth 1 https://github.com/fzfclee/consulting-skillsWrote 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/fzfclee/consulting-skills/force-field-analysis)<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/force-field-analysis"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/force-field-analysis/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/fzfclee/consulting-skills/force-field-analysis"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/force-field-analysis.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.00050 | $0.00729 |
| Opus 5.5 | $0.00020 | $0.00292 |
| Sonnet 5.5 | $0.00010 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
force-field-analysis 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Force Field Analysis
Use this skill to run Force Field Analysis as a practical consulting method, not as a generic framework explanation.
Method Notes
- List driving and restraining forces separately.
- Reducing a restraining force is often better than adding pressure.
Required Inputs
Collect or infer these inputs before execution:
- desired change
- supporting forces
- resisting forces
- stakeholders
- constraints
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use when the target change and relevant actors are unclear. Avoid generic pros-and-cons lists: each driving or restraining force needs evidence, relative strength, and a practical response.
Adjacent Methods
change-impact-analysis: assess affected groups, readiness, and adoption support.stakeholder-power-map: diagnose named sponsors, blockers, incentives, and vetoes.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
|---|---|---|---|
| Define change | Desired change, current state, target state. | State the behavior or decision that must shift. | Change statement. |
| List driving forces | Sponsors, incentives, pressures, benefits. | Identify forces pushing toward the change. | Driving-force list. |
| List restraining forces | Concerns, incentives, risks, capacity, politics. | Identify forces resisting the change. | Restraining-force list. |
| Score forces | Force lists and evidence. | Rate strength, addressability, owner, and evidence quality. | Force field map. |
| Choose levers | Force field map. | Decide which restraining forces to reduce and which driving forces to strengthen. | Change lever plan. |
Output Template
### 1. Change Objective
Desired change:
Current state:
Decision owner:
Time horizon:
### 2. Forces
| Force | Driver / restraint | Strength | Evidence | Controllability |
|---|---|---|---|---|
| | | | | |
### 3. Net Diagnosis
Dominant drivers:
Dominant restraints:
Fragile assumptions:
### 4. Intervention Plan
| Force to change | Move | Owner | Timing | Signal / side effect |
|---|---|---|---|---|
| | | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:
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 · 87 lines · 50 tokens per session scan A dc76409c4096
force-field-analysis is a skill published in the GitHub repository fzfclee/consulting-skills (7 stars, last pushed 15d ago), licensed Apache-2.0. It adds 50 tokens to every session and 729 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
ppt-keynote
An operating-model redesign for a scaling logistics firm — the diagnosis, the target model, and the transition roadmap. Built as a decision-grade consulting deck for client sponsor, ops leaders.
pipefy-process-design
Use this skill ONLY when the user explicitly asks for help designing or architecting a process ("help me design", "what's the best structure", "how do I organize this flow?"). For direct execution requests ("create a pipe for X", "build a reimbursement process", or any message with a detailed spec), skip this skill…
consistency-check
Verifies the V-Model artifact graph: Epics, Features, ADRs, PLANs, Backlog, Wayfinder rows, code refs. Syntactic and semantic modes. Explicit user command for "consistency check", "graph check", "dead links", "orphan features", or before a release; routine enforcement runs via the pre-commit hook, not per phase.
business-analysis
Condenses a structured dialog about problem, users, and scope into a short BA record that feeds requirements engineering. Use when the user mentions "Business Analysis", "BA", "Problem Analysis", "Personas", "Define Scope", "Explore", "How might we", "Value Proposition", or starts a new project without a clear…
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.
doblin-ten-types
Maps and designs innovation strategy using Doblin's Ten Types of Innovation across Configuration (Profit Model, Network, Structure, Process), Offering (Product Performance, Product System), and Experience (Service, Channel, Brand, Customer Engagement). Use when auditing current innovation profile, identifying…