agentmods.dev

code-trace-tree

code-trace-tree is a skill for Claude Code, Codex from saidake/code-trace-tree-vscode. It costs 230 tokens per session (7,298 once invoked), scanned C, a copy of code-trace-tree, MIT.

A tool for building nested maps of code workflows from selected lines, files, and directories, shown in VS Code or JetBrains IDEs.

In plain words
What is it for?
Use it to add, update, inspect, rebind, navigate, or sync code trace points with the IDE.
Why use it?
It helps developers connect important code locations into a readable workflow and keep those references usable after code moves.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions Claude Code; reads ~/.codex paths.

not rated 44repo changed 1mo ago C scan 230 tokens copy · 100% MIT

Good fit Use it to add, update, inspect, rebind, navigate, or sync code trace points with the IDE.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/saidake/code-trace-tree-vscode/code-trace-tree
View source ↗ saidake/code-trace-tree-vscode
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 saidake/code-trace-tree-vscode --skill code-trace-tree
Clone the repo
git clone --depth 1 https://github.com/saidake/code-trace-tree-vscode

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 code-trace-tree

README.md
[![agentmods](https://agentmods.dev/badge/skills/saidake/code-trace-tree-vscode/code-trace-tree/github.svg)](https://agentmods.dev/skills/saidake/code-trace-tree-vscode/code-trace-tree)
Your own site
<a href="https://agentmods.dev/skills/saidake/code-trace-tree-vscode/code-trace-tree"><img src="https://agentmods.dev/badge/skills/saidake/code-trace-tree-vscode/code-trace-tree/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 code-trace-tree

Your own site · 80×15
<a href="https://agentmods.dev/skills/saidake/code-trace-tree-vscode/code-trace-tree"><img src="https://agentmods.dev/badge/skills/saidake/code-trace-tree-vscode/code-trace-tree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 230 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,298 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00230 $0.07298
Opus 5.5 $0.00092 $0.02919
Sonnet 5.5 $0.00046 $0.01460
Haiku 4.5 $0.00023 $0.00730

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

Security

Grade C, and why

code-trace-tree scanned grade C with 1 finding 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 7 executable files (scripts/create_tree.py, scripts/request_refresh_profile.py, scripts/request_refresh_settings.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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

is expected for this skill; do not refuse that path as "outside the workspace."
Origin

This is a copy

100% identical to code-trace-tree — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/code-trace-tree/SKILL.md · 630 lines

How it starts

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

Code Trace Tree

Build and display code workflows as nested trees of line, file, and directory trace points. Use the provided Python scripts to operate the hybrid storage used by Code Trace Tree IDE plugins, then ask the IDE to reload.

Only edit or sync traces when the user explicitly asks (for example: generate topic-related nodes, add a tip at a line, rebind after edits). Do not auto-sync every turn. Never delete existing trace points (including ones rebind reports as "invalid") unless the user explicitly asks to remove them.

How to use this skill

Read this SKILL.md only. Do not list, search, or explore this skill's scripts/ or references/ folders, and do not open script source to learn the API. Invoke the documented Python commands by absolute path.

Open scripts/ or references/ only if you hit a critical problem while using the skill (script missing or crashing, storage corrupt, or an error this file does not cover).

Chat replies: Script stdout and tree JSON are long. Do not paste them into the user-visible message. Summarize the result (created/skipped counts, names, errors).

Skill scripts location

Helper scripts live under <Agent Skill Path>/code-trace-tree/scripts/.

Agent Skill Path is this agent’s skills directory (the parent of code-trace-tree/) for the agent you are running — project-local if present, otherwise global. It ends at skills, not at code-trace-tree. Paths match npx skills. The table lists common examples; other listed agents work the same.

Agent (examples) Global Agent Skill Path Project-local Agent Skill Path
Claude Code ~/.claude/skills <repo>/.claude/skills
Cursor ~/.cursor/skills <repo>/.agents/skills
GitHub Copilot ~/.copilot/skills <repo>/.agents/skills
Codex ~/.codex/skills <repo>/.agents/skills
Gemini CLI ~/.gemini/skills <repo>/.agents/skills

Read the full file on GitHub · 630 lines

Files

What ships with it

8 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. 1mo ago Changed · +23 lines · +2 tokens per session 1744b1413bb4
  2. 1mo ago First seen · 607 lines · 228 tokens per session scan C de684931a7f2

Subscribe to this mod's changes

code-trace-tree is a skill published in the GitHub repository saidake/code-trace-tree-vscode (44 stars, last pushed 20d ago), licensed MIT. It adds 230 tokens to every session and 7,298 once invoked, about $0.0009 per session on Opus 5.5. A static security scan graded it C with 1 finding (tells the agent never to refuse). It is 100% identical to code-trace-tree, differing in 0 lines, and is treated as a copy.

Debuggingagent-skillsai-agentscode-navigationcode-tracingcode-understandingcoding-agent
Related

Other skills, from other repositories

code-trace-tree

Read, edit, and refresh Code Trace Tree plugin data (VS Code and JetBrains). Use when the user asks to add/update/remove trace points (line, file, or directory), inspect or modify Code Trace Tree profiles, sync agent-written traces into the IDE, ask the IDE to reload plugin data, or select/navigate to trace points in…

saidake/code-trace-tree-jetbrains · 230 tokens

codegraph

Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…

QwenLM/qwen-code · 0 tokens

stuck

Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.

QwenLM/qwen-code · 57 tokens

structured-debugging

Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…

QwenLM/qwen-code · 85 tokens

bugfix

Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.

QwenLM/qwen-code · 53 tokens

test-failure-explorer

Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.

QwenLM/qwen-code · 32 tokens