trace

A command for viewing or exporting privacy-filtered Computer Use activity traces. A trace is a record of actions taken during a computer-use session, and the command supports status, listing recent traces, and confirmed export.

In plain words
What is it for?
Use it to check trace status, list recent traces, or export a redacted trace after confirming where the file should be saved.
Why use it?
It helps inspect or save session history while excluding screenshots, typed content, clipboard data, passwords, and full user paths. Export requires confirming the destination path.

Command

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/plocr/reasonix-computer-use/trace
Clone the repo
git clone --depth 1 https://github.com/Plocr/Reasonix-computer-use
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 101 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.00011 $0.00101
Opus 5 $0.00005 $0.00051
Sonnet 5 $0.00002 $0.00020
Haiku 4.5 $0.00001 $0.00010

Measured 2d ago against content hash 5cf2d5e9884d, 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 2d 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.

commands/trace.md · 9 lines

What it actually says

使用 computer_system(operation="trace") 处理 $ARGUMENTS。默认执行 statuslist 返回最近 轨迹;export 必须向用户确认目标路径后传 confirmed:true。说明导出内容不含截图、输入正文、 剪贴板、密码或完整用户路径。

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. 2d ago First seen · 9 lines · 11 tokens per session scan A 5cf2d5e9884d

Subscribe to this mod's changes

trace is a command published in the GitHub repository Plocr/Reasonix-computer-use (40 stars, last pushed 28d ago), licensed MIT. It adds 11 tokens to every session and 101 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.