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.
npx agentmods add commands/lanegrid/agtrace/sessiongit clone --depth 1 https://github.com/lanegrid/agtraceWhat 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 | $0.00000 | $0.00482 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
session 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 yesterday.
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.
What it actually says
agtrace session
Inspect and query historical AI coding agent sessions.
Overview
The session command provides tools to explore past sessions:
- List recent sessions for the current project
- Show detailed information about a specific session
- Analyze session structure, turns, and metrics
Commands
session list
List recent sessions for the current project.
agtrace session list [OPTIONS]
Output includes:
- Session ID
- Start time
- Duration
- Model used
- Turn count
- Context usage
Options:
--format json- Output in JSON format for programmatic use--limit N- Show only the N most recent sessions
Example:
agtrace session list --limit 10
agtrace session list --format json --limit 5
session show
Show detailed information about a specific session.
agtrace session show <SESSION_ID> [OPTIONS]
Output includes:
- Session metadata (ID, timestamps, model)
- Context window usage over time
- Turn-by-turn breakdown
- Tool usage summary
- Token counts and costs
Options:
--format json- Output in JSON format
Example:
agtrace session show abc123def456
agtrace session show abc123def456 --format json > session.json
Use Cases
Compare Sessions
Compare two sessions to understand what changed:
agtrace session show session1 --format json > s1.json
agtrace session show session2 --format json > s2.json
diff s1.json s2.json
Debug Context Pressure
Identify when context pressure became an issue:
agtrace session show <SESSION_ID>
# Look for high context usage percentages in the output
Analyze Tool Usage
See which tools were called and when:
agtrace session show <SESSION_ID> --format json | jq '.turns[].steps[] | select(.type == "tool_call")'
See Also
- watch - Live session monitoring
- lab - Advanced history search
- FAQ: CWD-Scoped Monitoring
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.
- yesterday First seen · 98 lines · 0 tokens per session scan A cf17537e8236
session is a command published in the GitHub repository lanegrid/agtrace (59 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 482 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.
Other commands, from other repositories
spec-design
Create comprehensive technical design for a specification.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.