waveq AGENTS.md

Guidance for using WaveQ, a tool that reads signal values and timing from hardware simulation waveform files such as VCD files.

In plain words
What is it for?
Use it to inspect signals near a failure, check waveform timing, define clocks, and review signal values or changes over a time window.
Why use it?
It helps agents collect exact evidence from simulations without treating limited waveform data as proof that a communication protocol is correct.

Instructions file for CodexOpenCode

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 instructions/ishaandugar/waveq/agents-md
Clone the repo
git clone --depth 1 https://github.com/IshaanDugar/waveq

Made for: Codex, OpenCode.

Per session 199 This file is loaded in full into every session.
When invoked 199 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.

ModelPer sessionOnce invoked
Fable 5 $0.00199 $0.00199
Opus 5 $0.00100 $0.00100
Sonnet 5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured yesterday against content hash 3d1c0c1a591a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

waveq 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 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.

AGENTS.md · 22 lines

What it actually says

WaveQ usage guidance for AI agents

Use WaveQ for exact VCD observations, not for protocol proof.

Preferred flow:

  1. Call configure_waveform once for the target .vcd or .vcd.gz.
  2. Call waveform_info to learn the timescale and range.
  3. Use resolve_signals before querying approximate or leaf-only names.
  4. Prefer values_at, changes_many, and window_digest over many single-signal calls.
  5. Call define_clock before cycle-based tools.
  6. Treat ok: false as a hard failure. Do not continue as though the query succeeded.
  7. Do not infer protocol correctness unless the queried evidence directly supports it.

Good first query near a failure:

window_digest(center_time=<failure time>, radius=<small window>, scope=<suspected block>)

Then follow up with exact values and changes for the small set of relevant signals.

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. yesterday First seen · 22 lines · 199 tokens per session scan A 3d1c0c1a591a

Subscribe to this mod's changes

waveq AGENTS.md is an instructions file published in the GitHub repository IshaanDugar/waveq (1 stars, last pushed 1mo ago), licensed MIT. It adds 199 tokens to every session, about $0.0010 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.