agentmods.dev

trace

trace is a command for Claude Code from agentrust-io/integrations. It costs 13 tokens per session (462 once invoked), scanned A, original, Apache-2.0.

A command that creates a signed report of the current Claude Code session, containing an Agent Manifest and a TRACE record. It also creates a public verification key for checking the signature.

In plain words
What is it for?
Use it to generate manifest.json, trace.json, and verification_key.json, then optionally verify the TRACE record with the supplied test command.
Why use it?
It provides a verifiable record of the session’s actual model, tools, and connected servers, helping others check that the report was not altered.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agentrust-claude-code plugin — 2 commands, 1 hook shipped together

not rated 5repo today A scan 13 tokens original Apache-2.0

Good fit Use it to generate manifest.json, trace.json, and verification_key.json, then optionally verify the TRACE record with the supplied test command.

Compare 6 commands from other repositories ↓
View source ↗ agentrust-io/integrations
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add agentrust-io/integrations
Claude Code
/plugin install agentrust-claude-code

Made for: Claude Code.

Or install agentrust-claude-code, the plugin that ships this one along with the rest of its 2 commands, 1 hook.

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/agentrust-io/integrations/trace/github.svg)](https://agentmods.dev/commands/agentrust-io/integrations/trace)
Your own site
<a href="https://agentmods.dev/commands/agentrust-io/integrations/trace"><img src="https://agentmods.dev/badge/commands/agentrust-io/integrations/trace/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 trace

Your own site · 80×15
<a href="https://agentmods.dev/commands/agentrust-io/integrations/trace"><img src="https://agentmods.dev/badge/commands/agentrust-io/integrations/trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 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.00013 $0.00462
Opus 5.5 $0.00005 $0.00185
Sonnet 5.5 $0.00003 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured 1mo ago against content hash 57769ff614cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

claude-code/commands/trace.md · 40 lines

What it actually says

You are running the AgenTrust report command. Generate a signed record of THIS session and explain it in plain English. Engine: ${CLAUDE_PLUGIN_ROOT}/engine/capture.py.

Steps:

  1. Ensure the signing packages are installed (once). Prefer the pinned set: pip install -r "${CLAUDE_PLUGIN_ROOT}/requirements.txt".
  2. Write this session's real facts to live.json. Use values you actually observe, never invented ones: model_id, model_provider, model_version, builtin_tools (your actual built-in tools), mcp_servers (the MCP servers actually connected now).
  3. Run python "${CLAUDE_PLUGIN_ROOT}/engine/capture.py" report --live-context live.json --out . This writes manifest.json, trace.json, and verification_key.json (the public key a third party uses to verify the manifest). The manifest is signed with the persistent key at ~/.claude/agentrust/signing_key.json; the private half never leaves the machine.
  4. Optionally confirm the TRACE record passes the suite: trace-tests verify --record trace.json --level 0 (or python -m trace_tests.cli verify --record trace.json --level 0 if the console script is not on PATH).

Then explain the report the user actually cares about:

  • what the agent IS: skills, tools, MCP, model, permissions, each fingerprinted.
  • what it DID this run: the TRACE record, software-only and Level 0 on a dev box.
  • whether anything changed since their approved baseline.
  • that the records are shareable: manifest.json verifies on any machine with verification_key.json, and trace.json passes the public conformance suite.

Be honest about scope. No TEE on a normal laptop means Level 0, not hardware attestation. The instruction-layer fingerprint covers CLAUDE.md and memory, not Claude Code's internal system prompt, which is not on disk.

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 · 40 lines · 13 tokens per session scan A 57769ff614cc

Subscribe to this mod's changes

trace is a command published in the GitHub repository agentrust-io/integrations (5 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 462 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-31.

Building agents
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

speckit.bug.fix

Apply the remediation from a bug assessment and record what was changed.

github/spec-kit · 12 tokens