method-framework-design

method-framework-design is a skill for Claude Code, Codex from EvoClaw/amplify. It costs 45 tokens per session (7,726 once invoked), scanned A, original, MIT.

A research planning workflow for designing a method, analysis framework, evaluation plan, and explanation of the project's contribution before coding or experiments begin.

In plain words
What is it for?
It helps choose between project types, design methods and analyses, plan evaluations, check related work, and define the research story.
Why use it?
It prevents researchers from using the wrong design path or starting implementation before the research question and evaluation are settled.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps choose between project types, design methods and analyses, plan evaluations, check related work, and define the research story.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/evoclaw/amplify/method-framework-design
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 EvoClaw/amplify --skill method-framework-design
Clone the repo
git clone --depth 1 https://github.com/EvoClaw/amplify

Made for: Claude Code, Codex.

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 method-framework-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/evoclaw/amplify/method-framework-design/github.svg)](https://agentmods.dev/skills/evoclaw/amplify/method-framework-design)
Your own site
<a href="https://agentmods.dev/skills/evoclaw/amplify/method-framework-design"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/method-framework-design/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 method-framework-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/evoclaw/amplify/method-framework-design"><img src="https://agentmods.dev/badge/skills/evoclaw/amplify/method-framework-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,726 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.00045 $0.07726
Opus 5.5 $0.00018 $0.03090
Sonnet 5.5 $0.00009 $0.01545
Haiku 4.5 $0.00005 $0.00773

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

Security

Grade A, and why

method-framework-design 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.

skills/method-framework-design/SKILL.md · 747 lines

How it starts

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

Method & Framework Design (Phase 3)

Overview

This is the most critical branching point in the research workflow. Type M and Type D projects follow completely different design paths. Executing the wrong path — or skipping design entirely — guarantees wasted effort.

On-Demand Literature Search (Active Throughout Phase 3)

  • "Has anyone tried approach X for this problem?"
  • "What's the current SOTA for sub-task Y?"
  • "Is there theoretical justification for design choice Z?"
  • "What hyperparameters did paper W use for this baseline?"

When this happens: SEARCH IMMEDIATELY. Do not guess, do not rely on memory, do not defer to "we'll check later." Use web search, arXiv, Google Scholar, or any available tools to find the answer NOW.

Update the literature record: Any new papers found during Phase 3 should be added to docs/02_literature/paper-list.md with a note: [Found during Phase 3 — method design].

If search fails (no results, paywall, or tools unavailable): do NOT fabricate an answer. Instead:

  1. Note the specific question that needs answering: "Need to know: [question]"
  2. Record it in the exploration report
  3. Ask the user: "I couldn't find information on [X]. Do you know, or can you check?"
  4. Continue with what you know, marking the gap as an assumption to verify

This applies equally to Phase 4, 5, and 6. Literature retrieval is a continuous activity, not a one-time Phase 1 task.

Re-Entry from Phase 4a (Exploratory Return Path)

If the user returns to Phase 3 from Phase 4a exploration (because baseline results or data analysis revealed the method/analysis design needs rethinking), do NOT start from scratch:

Read the full file on GitHub · 747 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. 1mo ago First seen · 747 lines · 45 tokens per session scan A b3fbd3add131

Subscribe to this mod's changes

method-framework-design is a skill published in the GitHub repository EvoClaw/amplify (11 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 7,726 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-30.