analysis-framing

analysis-framing is a skill for Claude Code from etoyama/insight-blueprint. It costs 59 tokens per session (2,018 once invoked), scanned A, original, MIT.

An analysis-planning guide that explores existing data, notes, and past analyses to help define a clear direction for investigation.

In plain words
What is it for?
Use it to inspect an existing .insight directory, find relevant data and analyses, and narrow a starting theme before designing a hypothesis.
Why use it?
It helps turn a broad or vague analysis topic into a focused question grounded in the information already available.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md; mentions subagents.

Part of the insight-blueprint plugin — 10 skills, 2 MCP servers shipped together

Good fit Use it to inspect an existing .insight directory, find relevant data and analyses, and narrow a starting theme before designing a hypothesis.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/etoyama/insight-blueprint/analysis-framing
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 etoyama/insight-blueprint --skill analysis-framing
Clone the repo
git clone --depth 1 https://github.com/etoyama/insight-blueprint

Made for: Claude Code.

Or install insight-blueprint, the plugin that ships this one along with the rest of its 10 skills, 2 MCP servers.

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 analysis-framing

README.md
[![agentmods](https://agentmods.dev/badge/skills/etoyama/insight-blueprint/analysis-framing/github.svg)](https://agentmods.dev/skills/etoyama/insight-blueprint/analysis-framing)
Your own site
<a href="https://agentmods.dev/skills/etoyama/insight-blueprint/analysis-framing"><img src="https://agentmods.dev/badge/skills/etoyama/insight-blueprint/analysis-framing/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 analysis-framing

Your own site · 80×15
<a href="https://agentmods.dev/skills/etoyama/insight-blueprint/analysis-framing"><img src="https://agentmods.dev/badge/skills/etoyama/insight-blueprint/analysis-framing.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 2,018 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.02018
Opus 5 $0.00030 $0.01009
Sonnet 5 $0.00012 $0.00404
Haiku 4.5 $0.00006 $0.00202

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

Security

Grade A, and why

analysis-framing 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 8d 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.

skills/analysis-framing/SKILL.md · 189 lines

How it starts

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

/analysis-framing --- Analysis Framing Explorer

Explores the .insight/ directory to discover available data, existing analyses, and domain knowledge, helping the user frame a well-grounded hypothesis direction. Does NOT create hypotheses --- that is /analysis-design's responsibility.

When to Use

  • Vague analysis theme, need to explore available data
  • Want to discover what data and existing analyses are available
  • Starting a new analysis direction, need grounding in existing context

When NOT to Use

  • Hypothesis is already clear --- use /analysis-design
  • Recording reasoning during analysis --- use /analysis-journal
  • Structured reflection on completed analysis --- use /analysis-reflection

Workflow

Step 1: Receive Theme

Accept the analysis theme from $ARGUMENTS or ask the user for one.

  • If $ARGUMENTS is provided, use it as the theme
  • If the theme is vague or overly broad (e.g., "データ分析", "社会問題"):
    • Present 2-3 candidate directions based on available data in .insight/catalog/
    • Ask the user to select or refine a direction before proceeding
    • Do NOT depend on development-partner for theme narrowing --- handle it independently
  • If forwarded from development-partner: accept the framing context from the conversation and build upon it
  • If an RQ Brief is present in the conversation (forwarded from /rq-problematization): use its テーマ as the theme and its 検証の方向性 as the seed direction. The research questions are theory-driven and not yet grounded — your job is to ground them in available data. Carry the central assumption forward into the Direction Dialogue (Step 4).
  • If .insight/ directory does not exist: inform the user that the project is not initialized and guide them to run insight-blueprint init. Stop the workflow here.

Step 2: Domain Exploration (Agentic Search)

Explore .insight/ directories to gather theme-relevant information. Do NOT use MCP tools. Use only Glob, Read, and Grep via Agent tool.

Read the full file on GitHub · 189 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. 8d ago First seen · 189 lines · 59 tokens per session scan A f736b5d025da

Subscribe to this mod's changes

analysis-framing is a skill published in the GitHub repository etoyama/insight-blueprint (0 stars, last pushed 16d ago), licensed MIT. It adds 59 tokens to every session and 2,018 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.