What is VeloQ AGENTS.md?

Contributor instructions for VeloQ, a command-line tool that reads performance reports and returns structured data. They describe the project layout, commands, coding rules, and data-format rules that contributors must preserve.

Use them when adding features, fixing bugs, refactoring VeloQ, or changing its support for Nsight Systems timelines, Nsight Compute kernel reports, or PyTorch profiler traces.

They give coding agents the project context needed to change VeloQ safely, especially when modifying its shared output format or adding commands.

How lucifer1004/VeloQ configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to lucifer1004/VeloQ. 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/lucifer1004/VeloQ/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/lucifer1004/VeloQ

Made for: Codex, OpenCode.

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/instructions/lucifer1004/veloq/agents-md.svg)](https://agentmods.dev/instructions/lucifer1004/veloq/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/lucifer1004/veloq/agents-md"><img src="https://agentmods.dev/badge/instructions/lucifer1004/veloq/agents-md.svg" alt="Measured on agentmods" height="20"></a>

Per session 7,150 This file is loaded in full into every session.

When invoked 7,150 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.07150	$0.07150
Opus 5	$0.03575	$0.03575
Sonnet 5	$0.01430	$0.01430
Haiku 4.5	$0.00715	$0.00715

Measured 6d ago against content hash ed895b80c3e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

VeloQ AGENTS.md 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 6d 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.

AGENTS.md · 498 lines

How it starts

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

VeloQ — Contributor Guidelines

This file is for agents/contributors developing VeloQ itself (adding verbs, profile sources, fixes, refactors). User-facing agents that use veloq as a black-box CLI to analyze profiles should read the skills under .agents/skills/:

.agents/skills/nsys-profile-analysis/ — Nsight Systems timelines
.agents/skills/ncu-profile-analysis/ — Nsight Compute kernel reports
.agents/skills/pytorch-profile-analysis/ — PyTorch/Kineto traces

The canonical repo-local Agent Skills source is plugins/veloq/skills/. The .agents/skills/ path is a compatibility alias for agent discovery.

VeloQ (velo-query) is a profile-query CLI family. Pure CLI in / JSON contract out by default, CSV/table projections for row-shaped views, no GUI, no MCP server in v1. Today it covers Nsight Systems (timeline traces), Nsight Compute (kernel reports), and experimental PyTorch/Kineto Chrome traces through a single binary with a shared envelope and pluggable ProfileSource trait. The PyTorch/Kineto source covers the Perfetto-style Chrome trace shape used by PyTorch profiler.

Wire-format invariants (do not break casually)

These constrain how every new verb/source must emit data. The user-facing contract description (with examples) lives in each skill's SKILL.md; this section is the maintainer-side rule set.

The JSON envelope and the per-source versions are VeloQ's public contract; the crate's 0.x Cargo version is independent of the wire version (breaking shape changes bump ENVELOPE_VERSION/source.version plus a CHANGELOG entry — see invariant 1; additive fields keep the version).

Envelope shape: veloq_core::Envelope<T> is the only success payload VeloQ writes on stdout, and veloq_core::EnvelopeError is the only error payload. Both carry schema / source / command / trace? / trace_span? / data | error. Error details always carry message and chain; typed diagnostics may additionally populate code and hint. Bump ENVELOPE_VERSION only on a breaking shape change; additive fields keep the same version.
Canonical list contract: every list-shaped response uses data: { count, total_matched, rows: Vec<Row>, auxiliary? }. Each Row carries a pub key: String composed from the row's identifying axes — see the per-verb format below. Non-primary data (per-mode common blocks, bucket histograms, …) goes under auxiliary. New verbs MUST conform — don't add a parallel list field with a different name. wire_format_smoke::every_primary_rows_item_carries_key structurally enforces the key presence across every Response type.

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

6d ago First seen · 498 lines · 7,150 tokens per session scan A ed895b80c3e2

Subscribe to this mod's changes

VeloQ AGENTS.md is an instructions file published in the GitHub repository lucifer1004/VeloQ (120 stars, last pushed 15d ago), licensed MIT. It adds 7,150 tokens to every session, about $0.0358 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-30.

GPU cli cuda ncu nsys profiling

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

VeloQ: Instructions file for Codex