Borrowing it
Nothing to install: this file belongs to tsz-org/tsz. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tsz-org/tsz/main/.agents/skills/tsz-tracing/SKILL.mdgit clone --depth 1 https://github.com/tsz-org/tszWrote 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/skills/tsz-org/tsz/tsz-tracing)<a href="https://agentmods.dev/skills/tsz-org/tsz/tsz-tracing"><img src="https://agentmods.dev/badge/skills/tsz-org/tsz/tsz-tracing/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.
<a href="https://agentmods.dev/skills/tsz-org/tsz/tsz-tracing"><img src="https://agentmods.dev/badge/skills/tsz-org/tsz/tsz-tracing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00046 | $0.00502 |
| Opus 5.5 | $0.00018 | $0.00201 |
| Sonnet 5.5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
tsz-tracing 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 23d 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.
What it actually says
TSZ Tracing
Use tracing before adding debug prints. It is for conformance failures, inference/narrowing/assignability surprises, and runtime path discovery.
Commands
TSZ_LOG=debug TSZ_LOG_FORMAT=tree cargo run -p tsz-cli -- file.ts
TSZ_LOG=debug TSZ_LOG_FORMAT=json cargo run -p tsz-cli -- file.ts
TSZ_LOG="tsz_solver=trace,tsz_checker=debug" TSZ_LOG_FORMAT=tree cargo run -p tsz-cli -- file.ts
TSZ_LOG="tsz_solver::narrowing=trace" TSZ_LOG_FORMAT=tree cargo run -p tsz-cli -- file.ts
Use RUST_LOG only as fallback. TSZ_LOG_FORMAT values: tree, json,
text.
Workflow
- Reduce to the smallest
.tswitness. - Compare expected behavior with
npx tsc --noEmit file.ts. - Start broad (
debug, tree), then narrow by module. - Capture large traces with
2> trace.log,head,tail,rg, orgrep "type_id=<id>". - Use structured trace fields and spans; never add ad-hoc stdout/stderr debugging.
Useful Filters
- Narrowing:
TSZ_LOG="tsz_solver::narrowing=trace". - Relations/inference:
TSZ_LOG="tsz_solver=debug". - Checker lookup/cache:
TSZ_LOG="tsz_checker=debug". - Query events:
TSZ_LOG=tsz::query_json=trace TSZ_LOG_FORMAT=json.
Read Output
Tree output nests spans, shows elapsed ms, level, module path, event, and fields. Look for the first structural divergence: wrong narrowed member, unexpected relation result, missing lazy ref resolution, cache hit/miss, or diagnostic source-span decision.
Tracing goes to stderr and is initialized only when TSZ_LOG/RUST_LOG is set.
For trace examples and quick reminders, read QUICKREF.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago First seen · 49 lines · 46 tokens per session scan A 149373c3c535
tsz-tracing is a skill published in the GitHub repository tsz-org/tsz (577 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 502 once invoked, about $0.0002 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-28.
Other skills, from other repositories
rust-check
Run cargo check on the current Rust project to find compile errors.
cli-wiring
Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.
ax-rust-signature
Use when writing Rust code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
hotpath_init
Configure hotpath profiling in a Rust project. Adds the hotpath dependency with feature-gated setup, instruments main with hotpath::main, functions with measure/measureall, and wraps channels, mutexes, rwlocks, streams, futures, reqwest clients, axum routers and byte-level I/O with hotpath macros. Use when the user…
ax-rust-llm
Use when writing Rust code with axllm for using the generated Ax package, factory functions, package docs, examples, and API reference.