trace

A repository memory command for saving notes, implementation context, and information about packages, files, and branches.

In plain words
What is it for?
Use it to initialize repository memory, add or update notes, retrieve relevant context, and connect Redis or SQL storage sources.
Why use it?
It preserves why changes were made and supports handoffs without relying on old chat messages.

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/d4rkninja/infynon-cli/trace
Clone the repo
git clone --depth 1 https://github.com/d4rkNinja/infynon-cli
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 732 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.00732
Opus 5 $0.00000 $0.00366
Sonnet 5 $0.00000 $0.00146
Haiku 4.5 $0.00000 $0.00073

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

docs/commands/trace.md · 74 lines

How it starts

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

trace

Use trace to save repo context, implementation notes, and package/file/branch memory.

When to use

Use Trace when you want to remember why a change happened, retrieve relevant repo context, or keep task handoff notes outside chat.

Basic usage

infynon trace <subcommand>

Common commands

Command Description
infynon trace overview Show Trace overview
infynon trace init Initialize Trace in the repo
infynon trace source add-redis <id> --url <url> Add Redis source
infynon trace source add-sql <id> --engine <engine> --url <url> Add SQL source
infynon trace source list List sources
infynon trace source default <id> Set default source
infynon trace source remove <id> Remove source
infynon trace note add <id> --title <title> --body <body> Add note
infynon trace note update <id> Update note
infynon trace note list List notes
infynon trace note remove <id> Remove note
infynon trace retrieve Retrieve notes by filters
`infynon trace sync --direction pull push
infynon trace compact Compact stale notes
`infynon trace schema sql redis`
infynon trace tui Open Trace TUI
infynon trace graph build Build knowledge graph
infynon trace graph show Show graph
infynon trace graph entity add <name> --kind <kind> Add graph entity
infynon trace graph entity list List graph entities
infynon trace graph entity remove <id> Remove graph entity
infynon trace graph edge add --from <a> --to <b> --relation <type> Add graph edge
infynon trace graph edge list List graph edges
infynon trace graph edge remove <id> Remove graph edge
infynon trace graph path <from> <to> Find path
infynon trace graph impact <entity> Show impact
infynon trace graph orphans Show unconnected entities
infynon trace graph diff <branch-a> <branch-b> Diff graphs
`infynon trace graph export --format json dot`
infynon trace graph import <file> Import graph
infynon trace graph tui Open graph TUI

Read the full file on GitHub · 74 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. 2d ago First seen · 74 lines · 0 tokens per session scan A 33c74bff168a

Subscribe to this mod's changes

trace is a command published in the GitHub repository d4rkNinja/infynon-cli (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 732 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-31.