methodology-extract

methodology-extract is a skill for Claude Code from fagemx/prismstack. It costs 238 tokens per session (2,464 once invoked), scanned A, original, MIT.

A method for extracting useful working principles from a user’s materials, code, or experience while focusing on a specific problem, rather than merely summarizing the material.

In plain words
What is it for?
Comparing a problem with source material, identifying reusable principles, combining team prompts or documents, and developing a methodology from repeated observations.
Why use it?
It turns scattered examples and team knowledge into practical guidance connected to the question being solved.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Comparing a problem with source material, identifying reusable principles, combining team prompts or documents, and developing a methodology from repeated observations.

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

Made for: Claude Code.

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 methodology-extract

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/fagemx/prismstack/methodology-extract"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/methodology-extract.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 238 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,464 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.00238 $0.02464
Opus 5.5 $0.00095 $0.00986
Sonnet 5.5 $0.00048 $0.00493
Haiku 4.5 $0.00024 $0.00246

Measured 2mo ago against content hash a59da97b02d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

methodology-extract 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 2mo 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/methodology-extract/SKILL.md · 272 lines

How it starts

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

/methodology-extract — Collision-Based Methodology Distillation

Role

You are a methodology distiller. You take the user's current problem and look at any material through that lens — extracting what's useful, discarding what's not. You don't summarize materials. You extract principles that help the user's specific situation.

Forbidden postures:

  • Do NOT enter questionnaire mode — don't ask the user questions one by one
  • Do NOT passively summarize — don't just describe what's in the material
  • Do NOT produce empty frameworks — don't give templates without content

How This Skill Works

This is NOT a Phase 1 -> 2 -> 3 skill. It's a collision-based interaction.

The loop:
  1. User brings A (problem/question/intuition) + B (material/experience/observation)
  2. You read B through the lens of A
  3. Extract what's useful for A from B
  4. Present your extraction to user for confirmation/correction
  5. Record as Collision Note
  6. When enough collisions accumulate -> synthesize into Methodology Note
  7. User may bring more B materials -> more collisions -> methodology evolves

Entry modes (detect, don't ask):

  • a) User has A + B → go straight to collision
  • b) User has A but no B → help find B (search, suggest references)
  • c) User has B but no explicit A → infer A from context (what are they working on?)
  • d) User just says "整理方法論" → read existing collisions, synthesize
  • e) User has multiple sources from different people → team consolidation mode(見下方)

Context Discovery (on start)

_SLUG=$(basename "$(git rev-parse --show-toplevel 2>/dev/null || pwd)")
_PROJECTS_DIR="${HOME}/.prismstack/projects/${_SLUG}"
_STATE_DIR="${_PROJECTS_DIR}/.prismstack"
_METH_DIR="docs/methodology"

# Check for existing methodology work
mkdir -p "$_METH_DIR/collisions" 2>/dev/null
_COLLISION_COUNT=$(ls "$_METH_DIR"/collisions/*.md 2>/dev/null | wc -l | tr -d ' ')
_HAS_METHODOLOGY=0
[ -f "$_METH_DIR/domain-methodology.md" ] && _HAS_METHODOLOGY=1

echo "COLLISIONS: $_COLLISION_COUNT"
echo "HAS_METHODOLOGY: $_HAS_METHODOLOGY"

Read the full file on GitHub · 272 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2mo ago First seen · 272 lines · 238 tokens per session scan A a59da97b02d7

Subscribe to this mod's changes

methodology-extract is a skill published in the GitHub repository fagemx/prismstack (1 stars, last pushed 6mo ago), licensed MIT. It adds 238 tokens to every session and 2,464 once invoked, about $0.0010 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.

Related

Other skills, from other repositories

technical-documentation

Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or…

wondelai/skills · 204 tokens

top-design

Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…

wondelai/skills · 113 tokens

crossing-the-chasm

Navigate the technology adoption lifecycle from early adopters to mainstream market. Use when the user mentions "crossing the chasm", "beachhead segment", "whole product", "early adopters vs mainstream", "tech go-to-market", "bowling pin strategy", "technology adoption lifecycle", "pragmatist buyers", "growth stalled…

wondelai/skills · 139 tokens

design-everyday-things

Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…

wondelai/skills · 132 tokens

design-sprint

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…

wondelai/skills · 137 tokens

hooked-ux

Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…

wondelai/skills · 109 tokens