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/sigistry/marketplace/trace-flowgit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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.
[](https://agentmods.dev/commands/sigistry/marketplace/trace-flow)<a href="https://agentmods.dev/commands/sigistry/marketplace/trace-flow"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/trace-flow.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.00637 |
| Opus 5 | $0.00008 | $0.00318 |
| Sonnet 5 | $0.00003 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
trace-flow 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace what actually happens when a user action or request runs, from entry point through routing, middleware, handlers, services, and data access, to the response. Use this to understand an unfamiliar path before you change it, or to explain a flow to a teammate. $ARGUMENTS names the action or entry point (e.g. "POST /checkout", "user clicks Export", "the nightly reconciliation job", "GraphQL updateProfile").
Process
Step 1: Find the entry point
Identify how the flow starts and where it is registered, do not assume a framework, detect it:
- HTTP/API: route tables, decorators/annotations (
@app.route,@GetMapping,router.post), OpenAPI specs, framework controllers. - GraphQL/RPC: resolver maps,
.protoservice definitions, schema-to-resolver wiring. - Events/jobs: queue subscribers, cron/scheduler registrations, message handlers.
- CLI/UI: command registration, or the client handler that issues the request.
Step 2: Follow the real call graph
Launch the flow-tracer agent with the entry point. It follows the actual chain, middleware and guards → handler → service/domain logic → data access and external calls → response serialization, resolving each hop through imports and call sites, and noting branches, retries, transactions, and side effects (events published, caches written, emails queued). Every hop is cited at file:line; it never fabricates a step it cannot find in the source.
Step 3: Report
Produce exactly these sections:
- Entry point: the trigger, its registration
file:line, and the input shape (route+method, event name, or command). - Step-by-step trace: one numbered step per hop: layer,
file:line, function signature, what it does, and any branch/side effect. Mark async/queued hops. - Data access & external calls: the reads/writes and third-party calls made along the path, each with
file:line. - Sequence diagram: a Mermaid
sequenceDiagramof the real path (participants = the actual components you traced, not a generic template).
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.
- 5d ago First seen · 34 lines · 15 tokens per session scan A c20045b6e591
trace-flow is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed yesterday), licensed MIT. It adds 15 tokens to every session and 637 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-31.
Other commands, from other repositories
build
Guided feature development with approval gates at each phase.
adv-codex
Send a prompt to Codex CLI and return the response.
make
Create structured implementation plan in docs/plans/.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
review
Pressure-test an important decision, plan, proposal, strategy, architecture, or recommendation with adaptive depth and token-efficient verification.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.