What is trace-matrix?

A workflow that compares backend code with a central checklist called MATRIX.md. It records which database, web, and Mac surfaces are affected by endpoints, data structures, pipeline stages, and other backend parts.

Use it to scan Go, protocol, Swift, and SQL files, then update verified surface marks for HTTP, gRPC, database, pipeline, and tuning areas.

It helps find missing or incorrect links between backend code and the parts of the product that consume it.

How banshee-data/velocity.report configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to banshee-data/velocity.report. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/banshee-data/velocity.report/main/.github/prompts/trace-matrix.prompt.md

Clone the repo

git clone --depth 1 https://github.com/banshee-data/velocity.report

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banshee-data/velocity.report/trace-matrix/github.svg)](https://agentmods.dev/commands/banshee-data/velocity.report/trace-matrix)

Your own site

<a href="https://agentmods.dev/commands/banshee-data/velocity.report/trace-matrix"><img src="https://agentmods.dev/badge/commands/banshee-data/velocity.report/trace-matrix/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banshee-data/velocity.report/trace-matrix"><img src="https://agentmods.dev/badge/commands/banshee-data/velocity.report/trace-matrix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,319 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.02319
Opus 5.5	$0.00014	$0.00928
Sonnet 5.5	$0.00007	$0.00464
Haiku 4.5	$0.00003	$0.00232

Measured 14d ago against content hash 29c9d522d95a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trace-matrix 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 14d 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.

.github/prompts/trace-matrix.prompt.md · 210 lines

How it starts

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

Workflow: trace-matrix

Maintain data/structures/MATRIX.md — the canonical mapping of every backend surface (HTTP endpoints, gRPC methods, DB tables/columns, pipeline stages, structs, tuning params, cmd/ entry points, debug routes) to three consumer surfaces: DB, Web, Mac.

Invoke with #trace-matrix in Copilot Chat, optionally specifying a task group: http, grpc, db, pipeline, tuning, or all.

Procedure

Step 1 — Generate the checklist

python3 scripts/list-matrix-fields.py --checklist

This scans Go, Proto, Swift, SQL, and selected repo metadata and outputs a markdown checklist across 5 task groups, each sized for one context window.

Step 2 — Read the current matrix

Read data/structures/MATRIX.md to understand existing surface marks. This file is the ground truth to update.

§11 is a reference inventory of Go report pipeline files only. Do not assign DB/Web/Mac surface marks to that section.

Step 3 — Trace one task group at a time

HTTP API Surfaces (§1, §2)

Sections: §1 Radar HTTP, §2 LiDAR HTTP

For each endpoint, read the Go handler function
Check DB: does the handler call any db.* or store.* method?
Check Web: search web/src/ for fetch() calls to this path
Check Mac: search tools/visualiser-macos/ for HTTP calls to this path

Key files:

internal/api/server.go — radar HTTP handlers
internal/lidar/server/routes.go — LiDAR route registration and core HTTP handlers
internal/lidar/server/track_api.go — track API handlers
internal/lidar/server/run_track_api.go — run/track API handlers
internal/lidar/server/clip_api.go — scene and evaluation handlers
internal/api/lidar_labels.go — label API handlers
web/src/lib/api/ — Svelte fetch calls
tools/visualiser-macos/VelocityVisualiser/ — Mac HTTP calls

gRPC + Proto Surfaces (§3, §14)

Sections: §3 gRPC methods, §14 FrameBundle proto fields

Read proto/velocity_visualiser/v1/visualiser.proto for method definitions
Check Go server impl in internal/lidar/grpc/ for DB reads
Search Swift client in tools/visualiser-macos/ for method calls
Almost all should be Mac=✅ only — flag any that also touch DB or Web

Read the full file on GitHub · 210 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.

14d ago Changed 29c9d522d95a
1mo ago First seen · 210 lines · 34 tokens per session scan A 0d35350ee806

Subscribe to this mod's changes

trace-matrix is a command published in the GitHub repository banshee-data/velocity.report (11 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 2,319 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-09-25.

Backend and APIs Databases lidar radar road-safety street-safety traffic-analysis urban-analytics

trace-matrix next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
trace-matrixbanshee-data/velocity.report	Command	11	today	Apache-2.0	A	34	GitHub Copilot
initfcakyon/claude-codex-settings	Command	1.2k	yesterday	Apache-2.0	A	0	Claude Code
toh-connectwasintoh/toh-framework	Command	96	2mo ago	MIT	A	12	Claude Code
model-createsmicolon/ai-kit	Command	7	1mo ago	MIT	A	13	Claude Code
servicesmgd34msu/goodvibes-plugin	Command	6	2mo ago	MIT	A	33	Claude Code
sparc-supabase-adminruvnet/ruv-FANN	Command	387	3mo ago	MIT	A	32	Claude Code
trex.kind.add-fieldopenshift-online/agent-control-plane	Command	13	4d ago	MIT	A	0	Claude Code

velocity.report: Command for GitHub Copilot