flinch-probe

Measure language model suppression of charged vocabulary via forward-pass log-probabilities.

1|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/daedalus/skills --skill flinch-probe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flinch-probe
Source: https://github.com/daedalus/skills/tree/main/skills/flinch-probe
Command: npx skills add https://github.com/daedalus/skills --skill flinch-probe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires torch, numpy, transformers, openai, anthropic, matplotlib, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Measures how much a language model suppresses charged vocabulary relative to fluency, enabling objective audits of model behavior and the detection of hidden censorship or bias in generated text.

Core Features & Use Cases

  • Six-axis flinch profiling across Anti-China, Anti-America, Anti-Europe, Slurs, Sexual, and Violence to quantify suppression.
  • Local or API-based probing using log-probabilities, with a fixed 0–100 flinch scale for cross-model comparisons.
  • Quick benchmarking against baselines and generation of visualizations (radar charts and per-axis reports) for governance and safety teams.

Quick Start

Run a full flinch scan on a compatible model and review the generated flinch_results.json and radar chart.

Frequently Asked Questions about flinch-probe

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is language model flinch measurement and how do logprobs detect vocabulary suppression?

Flinch measurement quantifies vocabulary suppression by comparing forward-pass log-probabilities for target words across a fixed six-axis corpus. It calculates per-term and per-axis suppression on a 0–100 scale to detect hidden censorship or bias in generated text.

How do I measure LLM bias across specific categories like violence or slurs?

You can measure LLM bias by running a six-axis flinch profiling scan across Anti-China, Anti-America, Anti-Europe, Slurs, Sexual, and Violence categories. The tool computes log-probabilities for charged vocabulary to output a structured JSON and optional radar charts for comparison.

Can I use API-based logprob sampling to evaluate vocabulary suppression without local HuggingFace models?

Yes, the tool supports API-based probing using log-probabilities from providers like OpenAI and Anthropic, or local HuggingFace transformers-based inference. Both methods compute flinch on a fixed 0–100 scale for cross-model comparisons.

How do I benchmark and visualize language model censorship differences across multiple models?

You can benchmark against baselines and generate visualizations using radar charts and per-axis reports. The tool outputs a structured flinch_results.json alongside optional visualizations for governance and safety teams to compare cross-model suppression.

What do I need to run a flinch scan and audit model safety behavior?

You need access to a corpus.json, a compatible model, and either local transformers-based inference or API-based logprob sampling. The tool implements the exact measurement workflow described in the provided flinch corpus and scoring rules.

Why does my language model suppress charged vocabulary relative to its general fluency?

Language models suppress charged vocabulary relative to fluency due to hidden censorship or bias in training or alignment. Measuring forward-pass log-probabilities for target words across a fixed six-axis corpus enables objective audits of this model behavior.