agentmods.dev

trace

trace is a command for coding agents from nguyenthienthanh/aura-frog. It costs 0 tokens per session (1,187 once invoked), scanned A, original, MIT.

A command that displays an agent task's activity record, including files read, claims made, tool calls, and decisions. It can also show claims that were not grounded in recorded evidence.

In plain words
What is it for?
Use it to inspect a task's full trace, review only file reads or unsupported claims, or examine recent activity.
Why use it?
It makes the agent's work easier to inspect and helps reveal unsupported statements. Filters can narrow the output to particular event types or recent entries.

Command

Part of the aura-frog plugin — 17 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers shipped together

not rated 24 9d ago A scan 0 tokens original MIT
View the source file nguyenthienthanh/aura-frog
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 commands/nguyenthienthanh/aura-frog/trace
Clone the repo
git clone --depth 1 https://github.com/nguyenthienthanh/aura-frog

Or install aura-frog, the plugin that ships this one along with the rest of its 17 skills, 24 commands, 15 agents, 10 hooks, 6 MCP servers.

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 trace

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/trace.svg)](https://agentmods.dev/commands/nguyenthienthanh/aura-frog/trace)
Your own site
<a href="https://agentmods.dev/commands/nguyenthienthanh/aura-frog/trace"><img src="https://agentmods.dev/badge/commands/nguyenthienthanh/aura-frog/trace.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,187 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.00000 $0.01187
Opus 5 $0.00000 $0.00593
Sonnet 5 $0.00000 $0.00237
Haiku 4.5 $0.00000 $0.00119

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

Security

Grade A, and why

trace 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 3d 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.

aura-frog/commands/trace.md · 70 lines

How it starts

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

/aura-frog:trace

Render the reasoning trace for a task — file_reads, output_claims, tool_calls, decisions. Surfaces hallucinations (claims with grounded: false).

Usage

/aura-frog:trace <TASK_ID>                          # full trace, table format
/aura-frog:trace <TASK_ID> --filter file_read       # one event type only
/aura-frog:trace <TASK_ID> --hallucinations         # only output_claim events with grounded:false
/aura-frog:trace <TASK_ID> --tail 50                # last N events
/aura-frog:trace <TASK_ID> --since 2026-04-29T12:00:00Z
/aura-frog:trace --active                            # use the active.task from .claude/plans/active.json

Protocol

  1. Resolve TASK_ID. If --active, read .claude/plans/active.json → active.task. Refuse if no active task.

  2. Locate the trace file. Since v3.7.3 the trace is co-located with the task, so resolve the task folder first and only then fall back to the legacy flat path — the same order resolveTracePaths() in hooks/tool-call-tracer.cjs uses, which is what both writers (tool-call-tracer.cjs and tdd-red-failure-tracker.cjs) follow:

    1. Find the task folder: the directory under .claude/plans/features/*/stories/*/tasks/ whose task.md frontmatter has id: {TASK_ID}. If found → read {taskFolder}/trace.jsonl.
    2. Otherwise → read the legacy .claude/plans/traces/{TASK_ID}.jsonl.
    3. If neither exists → exit with message "no trace yet for {TASK_ID}".

    Read only the first location that exists; do not merge the two. A legacy file alongside a task folder is a pre-v3.7.3 leftover, and reporting it as the live trace would show a stale event stream.

  3. Parse each line as JSON. Filter by --filter and --since flags.

  4. Render table (columns: ts, event_id, type, summary). For long payloads (>80 chars), truncate with ….

  5. Halluciation summary: count of output_claim with grounded:false. If > 0 in non---hallucinations mode, print: ⚠️ N potential hallucinations — re-run with --hallucinations to see them.

  6. Storage warning: if trace file > 10 MB or > 1000 events → suggest /aura-frog:plan-archive (Milestone C).

Read the full file on GitHub · 70 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. 3d ago First seen · 70 lines · 0 tokens per session scan A 5b86385c2892

Subscribe to this mod's changes

trace is a command published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,187 tokens. 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 agentsai-assisted-developmentai-for-developersclaude-codecode-qualitycontext-engineeringdeveloper-productivity
Related

Other commands, from other repositories

review-agentready

AgentReady-specific code review with attribute mapping and score impact analysis.

ambient-code/agentready · 12 tokens

review-pr

Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.

hoblin/claude-ruby-marketplace · 39 tokens

create_plan

Create detailed implementation plans through interactive research and iteration.

hoblin/claude-ruby-marketplace · 9 tokens

research_codebase

Document codebase as-is with thoughts directory for historical context.

hoblin/claude-ruby-marketplace · 11 tokens

iterate_plan

Iterate on existing implementation plans with thorough research and updates.

hoblin/claude-ruby-marketplace · 11 tokens

resume_handoff

Resume work from handoff document with context analysis and validation.

hoblin/claude-ruby-marketplace · 11 tokens