appreciative-inquiry

appreciative-inquiry is a skill for Claude Code from fatihguner/foreman. It costs 84 tokens per session (3,268 once invoked), scanned A, original, MIT.

A problem-solving and planning framework that starts by identifying what is already working well and building on it.

In plain words
What is it for?
Use it for team discussions, organisational planning, reflection, and change work.
Why use it?
It shifts attention away from problems alone, which can help groups find practical improvements from existing strengths.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the foreman plugin — 142 skills, 60 commands, 7 agents shipped together

Good fit Use it for team discussions, organisational planning, reflection, and change work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fatihguner/foreman/appreciative-inquiry
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 fatihguner/foreman --skill appreciative-inquiry
Clone the repo
git clone --depth 1 https://github.com/fatihguner/foreman

Made for: Claude Code.

Or install foreman, the plugin that ships this one along with the rest of its 142 skills, 60 commands, 7 agents.

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 appreciative-inquiry

README.md
[![agentmods](https://agentmods.dev/badge/skills/fatihguner/foreman/appreciative-inquiry/github.svg)](https://agentmods.dev/skills/fatihguner/foreman/appreciative-inquiry)
Your own site
<a href="https://agentmods.dev/skills/fatihguner/foreman/appreciative-inquiry"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/appreciative-inquiry/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 appreciative-inquiry

Your own site · 80×15
<a href="https://agentmods.dev/skills/fatihguner/foreman/appreciative-inquiry"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/appreciative-inquiry.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,268 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00084 $0.03268
Opus 5 $0.00042 $0.01634
Sonnet 5 $0.00017 $0.00654
Haiku 4.5 $0.00008 $0.00327

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

Security

Grade A, and why

appreciative-inquiry 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 3d 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.

plugins/foreman/skills/appreciative-inquiry/SKILL.md · 227 lines

How it starts

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

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Appreciative Inquiry

Stop fixing problems. The orthodox approach to organisational change -- diagnose what is broken, analyse root causes, prescribe solutions -- carries an unexamined assumption: that progress comes from eliminating deficits. David Cooperrider, working at Case Western Reserve University in the 1980s, proposed something radical. What if the fastest path to transformation is not fixing weaknesses but systematically amplifying strengths? What if the questions you ask determine the reality you find -- and organisations that ask "what is wrong?" get very good at cataloguing dysfunction, while organisations that ask "what works brilliantly, and how do we get more of it?" generate energy, alignment, and change that deficit-based approaches rarely achieve?

This is not positive thinking. Appreciative Inquiry (AI) is a structured methodology backed by four decades of organisational research. It does not deny problems; it reframes the unit of analysis. Rather than treating the organisation as a machine with broken parts, AI treats it as a living system whose best moments contain the DNA of its future. The shift is neither naive nor cosmetic -- it is epistemological.


The Framework

The Core Principle: The Constructionist Premise

Appreciative Inquiry rests on a foundational claim: organisations move in the direction of the questions they ask. Questions are not neutral instruments of discovery; they are interventions that shape what people notice, discuss, and ultimately create. An organisation that habitually asks "why did we fail?" develops sophisticated failure narratives. An organisation that asks "when did we succeed against the odds, and what made that possible?" develops actionable success patterns.

This is not a rejection of critical analysis. It is a recognition that the inquiry itself is generative -- it creates the conditions for the reality it investigates.

Read the full file on GitHub · 227 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. 3d ago Changed · +226 lines · +84 tokens per session d45147336cea
  2. 9d ago First seen · 1 lines · 0 tokens per session scan A 0b8eae7c0a21

Subscribe to this mod's changes

appreciative-inquiry is a skill published in the GitHub repository fatihguner/foreman (48 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 3,268 once invoked, about $0.0004 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.

Related

Other skills, from other repositories