What is reasoning-trace-optimizer?

A guide for finding and improving problems in an AI agent's decision process. It examines the agent's reasoning history, instructions, tool use, and repeated failures.

Use it to investigate context degradation, tool confusion, instruction drift, repeated task failures, and performance regressions.

It helps explain why an agent gives poor results or loses focus over time. It turns those observations into prompt changes that can be tested again.

reasoning-trace-optimizer — Skill by muratcankoylan

About the project

Agent Skills for Context Engineering is a collection of reusable instructions that teach AI agents how to manage their context, coordinate multi-agent systems, and evaluate behavior. Developers use it when building or debugging production agent systems, and the catalogue entries are skills, agents, instructions, and a plugin from this collection.

muratcankoylan/Agent-Skills-for-Context-Engineering · 18,146 stars · on GitHub

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 muratcankoylan/Agent-Skills-for-Context-Engineering --skill interleaved-thinking

Clone the repo

git clone --depth 1 https://github.com/muratcankoylan/Agent-Skills-for-Context-Engineering

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking/github.svg)](https://agentmods.dev/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking)

Your own site

<a href="https://agentmods.dev/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking"><img src="https://agentmods.dev/badge/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking"><img src="https://agentmods.dev/badge/skills/muratcankoylan/agent-skills-for-context-engineering/interleaved-thinking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,373 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00035	$0.01373
Opus 5.5	$0.00014	$0.00549
Sonnet 5.5	$0.00007	$0.00275
Haiku 4.5	$0.00003	$0.00137

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

Security

Grade A, and why

reasoning-trace-optimizer 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.

The scan reads SKILL.md. This mod also ships 11 executable files (examples/01_basic_capture.py, examples/02_tool_usage.py, examples/03_full_optimization.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

examples/interleaved-thinking/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.

Reasoning Trace Optimizer

Debug and optimize AI agents by analyzing their reasoning traces. This skill uses MiniMax M2.1's interleaved thinking to provide deep insight into agent decision-making and generate concrete improvements.

When to Activate

Agent reasoning traces need debugging, analysis, or prompt optimization
Agent task fails and user wants to understand why
User mentions "context degradation", "tool confusion", or "instruction drift"
Request to improve agent performance or reduce errors
User wants to generate shareable learnings from debugging sessions
After repeated failures on similar tasks

Core Concepts

Interleaved Thinking

Unlike standard reasoning models that think once at the start, interleaved thinking allows reasoning BETWEEN each tool interaction. This is critical because:

Long-horizon tasks require maintaining focus across many turns
External perturbations (tool outputs, environment changes) need real-time adaptation
Debugging requires seeing HOW decisions were made, not just WHAT was output

The Optimization Loop

Execute Agent → Capture Traces → Analyze Patterns → Optimize Prompt → Re-run
                                                          ↑____________|

Each iteration improves the prompt based on detected patterns until convergence.

Pattern Detection

Common failure patterns the analyzer detects:

Pattern	Description
`context_degradation`	Model loses track of information over long contexts
`tool_confusion`	Model misunderstands tool capabilities or outputs
`instruction_drift`	Model gradually deviates from original instructions
`goal_abandonment`	Model stops pursuing the original goal
`circular_reasoning`	Model repeats similar actions without progress
`premature_conclusion`	Model concludes before completing the task

Usage Modes

Mode 1: M2.1 Agent Debugging

Run a task through M2.1 and analyze its reasoning:

Read the full file on GitHub · 222 lines

Files

What ships with it

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

1mo ago First seen · 222 lines · 35 tokens per session scan A 6d330b7afc13

Subscribe to this mod's changes

reasoning-trace-optimizer is a skill published in the GitHub repository muratcankoylan/Agent-Skills-for-Context-Engineering (18,146 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 1,373 once invoked, about $0.0001 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.

Building agents Debugging

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

deck-retro

Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…

asheshgoplani/agent-deck · 86 tokens