prioritization

prioritization is a skill for Claude Code, Codex from openscientist-io/openscientist. It costs 15 tokens per session (1,455 once invoked), scanned A, original, Apache-2.0.

A decision-making guide for choosing what to investigate next during research or data analysis. It ranks hypotheses by expected impact, feasibility, and newness, while also identifying when broader exploration is useful.

In plain words
What is it for?
It helps prioritize hypotheses to test, decide when to explore data, and choose the next investigation when several research paths are available.
Why use it?
It helps researchers focus limited time on questions most likely to produce useful evidence instead of pursuing options at random.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/openscientist-io/openscientist/prioritization
Any agent
npx skills add openscientist-io/openscientist --skill prioritization
Clone the repo
git clone --depth 1 https://github.com/openscientist-io/openscientist

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 prioritization

README.md
[![agentmods](https://agentmods.dev/badge/skills/openscientist-io/openscientist/prioritization.svg)](https://agentmods.dev/skills/openscientist-io/openscientist/prioritization)
Your own site
<a href="https://agentmods.dev/skills/openscientist-io/openscientist/prioritization"><img src="https://agentmods.dev/badge/skills/openscientist-io/openscientist/prioritization.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,455 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.01455
Opus 5 $0.00008 $0.00727
Sonnet 5 $0.00003 $0.00291
Haiku 4.5 $0.00002 $0.00145

Measured 4d ago against content hash 4c6659c784fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

prioritization 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 4d 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/workflow/prioritization/SKILL.md · 222 lines

How it starts

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

Prioritization

When to Use This Skill

  • When you have multiple hypotheses and need to choose which to test first
  • When you're deciding between exploring new areas vs deepening current investigation
  • When iteration budget is running low and you need to focus

The Core Question

"What will provide the most scientific insight right now?"

Prioritization Framework

Option 1: Test a Hypothesis

Priority = Impact × Feasibility × Novelty

Rate each hypothesis:

  • Impact (1-5): How central to research question?
  • Feasibility (1-5): Can we test it with current data?
  • Novelty (1-5): Is this a new insight?

Test highest-scoring hypothesis first.

Example:

H1: "Salvage flux is increased"
  Impact=4, Feasibility=4, Novelty=3 → Score=48

H2: "CMP→CDP bottleneck"
  Impact=5, Feasibility=5, Novelty=4 → Score=100 ⭐ Test this

H3: "Sex differences modulate effect"
  Impact=2, Feasibility=3, Novelty=2 → Score=12

Option 2: Explore Data

When to prioritize exploration:

  • ✅ Early iterations (< 10% of budget)
  • ✅ You're stuck and need fresh ideas
  • ✅ Current hypotheses are all low-priority
  • ✅ You haven't looked at key variable types yet

When NOT to explore:

  • ❌ Late iterations (> 80% of budget)
  • ❌ You have high-priority hypotheses ready to test
  • ❌ You're avoiding testing a difficult hypothesis

Option 3: Search Literature

When to prioritize literature:

  • ✅ Before testing a hypothesis (to inform design)
  • ✅ After unexpected result (to understand mechanism)
  • ✅ When hypothesis was rejected (to generate alternatives)
  • ✅ Early iterations (build knowledge foundation)

When NOT to search:

  • ❌ As procrastination (avoiding analysis)
  • ❌ Late iterations when you should be synthesizing
  • ❌ You already searched this topic

Option 4: Record/Synthesize Findings

When to prioritize synthesis:

  • ✅ You've confirmed a finding but haven't recorded it
  • ✅ Late iterations (> 70% of budget)
  • ✅ You have 3+ findings that might be related
  • ✅ You're approaching iteration limit

Read the full file on GitHub · 222 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. 4d ago First seen · 222 lines · 15 tokens per session scan A 4c6659c784fa

Subscribe to this mod's changes

prioritization is a skill published in the GitHub repository openscientist-io/openscientist (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 1,455 once invoked, about $0.0001 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

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

development

开发语言能力索引。Python、Go、Rust、TypeScript、Java、C++、Shell。当用户提到编程、开发、代码、语言时路由到此。.

fengshao1227/ccg-workflow · 41 tokens

post-build-flow

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

n8n-io/n8n · 53 tokens

n8n:human-like-code-review

Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.

n8n-io/n8n · 70 tokens

n8n:create-pr

Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.

n8n-io/n8n · 50 tokens

flow-next-resolve-pr

Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.

gmickel/flow-next · 36 tokens