analyze

analyze is a skill for Claude Code, Codex from janrummel/claude-orchestrator-starter. It costs 61 tokens per session (538 once invoked), scanned A, original, MIT.

A structured method for investigating a difficult question in repeated stages: plan what to find, gather information, review what you learned, and continue if needed.

In plain words
What is it for?
Use it for research, evaluation, deep dives, and other multi-step questions that need evidence and a reasoned conclusion.
Why use it?
It reduces guesswork by making the investigation's goal, missing information, intermediate findings, and final conclusion explicit.

Skill for Claude CodeCodex

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

Good fit Use it for research, evaluation, deep dives, and other multi-step questions that need evidence and a reasoned conclusion.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/janrummel/claude-orchestrator-starter/analyze
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 janrummel/claude-orchestrator-starter --skill analyze
Clone the repo
git clone --depth 1 https://github.com/janrummel/claude-orchestrator-starter

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 analyze

README.md
[![agentmods](https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/analyze/github.svg)](https://agentmods.dev/skills/janrummel/claude-orchestrator-starter/analyze)
Your own site
<a href="https://agentmods.dev/skills/janrummel/claude-orchestrator-starter/analyze"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/analyze/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 analyze

Your own site · 80×15
<a href="https://agentmods.dev/skills/janrummel/claude-orchestrator-starter/analyze"><img src="https://agentmods.dev/badge/skills/janrummel/claude-orchestrator-starter/analyze.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 538 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.00061 $0.00538
Opus 5.5 $0.00024 $0.00215
Sonnet 5.5 $0.00012 $0.00108
Haiku 4.5 $0.00006 $0.00054

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

Security

Grade A, and why

analyze 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.

orchestrator/skills/analyze/SKILL.md · 69 lines

What it actually says

Analyze — ReAct Analysis Agent

You work like a reflective agent: Plan, Act, Reflect — in a repeatable analysis cycle.

Core Principles

  1. Planning before action — clarify goal and sub-questions first
  2. Tool usage only with clear intent
  3. Reflection is mandatory, not a bonus
  4. Reasoned conclusions instead of mere assertions

The ReAct Cycle

Phase 1: PLANNING

  1. Clarify the task goal (What should be understood/decided at the end?)
  2. Define sub-questions
  3. Knowledge check:
    • Check existing knowledge in conversation
    • Search Obsidian vault if available
    • Check knowledge database if available
    • Search episodic memory for past discussions
    • Result: What is known? What gaps remain? Use external sources only for gaps.
  4. Briefly outline approach — transparent for the user

Phase 2: ACTION

  1. Gather information step by step according to plan
  2. Name intermediate steps ("I'm now searching...", "I'm evaluating...")
  3. Minimize assumptions — prefer research
  4. Briefly note results per step

Phase 3: REFLECTION

  1. What do we know now? — Summarize learnings
  2. Is it enough? — Check if the task is sufficiently answered
  3. What's missing? — Identify new questions or blind spots
  4. Another cycle? — Decide if a new planning round is needed

Repeat or Output

  • If more depth needed: Start new cycle
  • If sufficient: Present structured result

Output Format

## Question
[What was analyzed?]

## Approach
[Which steps were taken?]

## Findings
[Structured results]

## Reflection
- **Confirmed:** [What is established]
- **Uncertain:** [What remains open]
- **Next steps:** [What could be investigated further]

Rules

  • Always make transparent where in the cycle we are
  • Break complex topics into traceable stages
  • The thinking process is visible — no "magic leaps"
  • At the end: suggest /signal-check for quality review
  • Tone: Analytical, methodical, transparent
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 · 69 lines · 61 tokens per session scan A ce20162691ef

Subscribe to this mod's changes

analyze is a skill published in the GitHub repository janrummel/claude-orchestrator-starter (5 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 538 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-31.

Related

Other skills, from other repositories