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 skills/tracewayapp/traceway/integration-testnpx skills add tracewayapp/traceway --skill integration-testgit clone --depth 1 https://github.com/tracewayapp/tracewayWhat 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.00090 | $0.02487 |
| Opus 5 | $0.00045 | $0.01243 |
| Sonnet 5 | $0.00018 | $0.00497 |
| Haiku 4.5 | $0.00009 | $0.00249 |
Grade A, and why
integration-test 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 2d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
integration-test — traceway-cli
A repeatable protocol for verifying the CLI end-to-end against a live Traceway server, focused on the things the Go smoke suite can't easily cover.
Trigger
Invoke ONLY when the user explicitly asks. Never run as a side effect of edits, commits, or builds.
Relationship to the Go smoke suite
The just smoke-test target (test/smoke/*_test.go, build tag smoke) is the primary regression check. Against a live instance it already covers:
- JSON shape of every list endpoint and
profiles list. - Output-format coverage (json/table/yaml) for projects, profiles, exceptions, endpoints, logs.
- Client-side enum validation (
--search-type,--order-by,--sort-direction,--aggregation,--tag). - Time-range parsing edges (
--since 7D, missing--to,--since+ absolute mix, far-future windows). metrics querymissing--name, bogus name → empty series, malformed tag.exceptions show <zeros>→ exit 5not_found.--profile no-such-profile→ exit 4;--project 0…0→ non-zero, no panic, noconnection_failed.
Do not re-implement these here. If they regress, that's a Go-test bug, not a skill failure.
What this skill adds beyond just smoke-test:
- Real-data detail endpoints —
exceptions show <captured-hash>, populatedmetrics query --name <real>with every aggregation + group-by. - Adaptive metric-name discovery — walk a candidate list until one populates.
- TTY-vs-pipe default — table rendering to a real terminal.
- Coverage matrix report — a human-readable artifact, on demand.
- Safety doctrine — the forbidden-verb blocklist and
confirmMutationenv hygiene, applied to every probe.
Hard constraints
Read-only. No exceptions. Even if a subcommand looks safe by name, check --help for mutating flags before running.
Forbidden verbs and flags
Skip any subcommand whose name or --help mentions:
archive,unarchive,resolve,unresolve,mute,ack,acknowledgecreate,delete,update,set,put,post,add,remove,rmassign,claim,close,reopenlogin,logout,token,rotate,regenerate--archive,--resolve,--delete,--write,--mutate,--apply,--commit
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.
- 2d ago First seen · 197 lines · 90 tokens per session scan A 463ca681d6d1
integration-test is a skill published in the GitHub repository tracewayapp/traceway (1,446 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 2,487 once invoked, about $0.0005 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.
Other skills, from other repositories
opentelemetry-docs
OpenTelemetry — vendor-neutral observability: traces, metrics, logs, OTLP, Collector, SDKs, semantic conventions.
netdata-otel-setup
Use when enabling the Netdata otel.plugin, writing /etc/netdata/otel.yaml, defining metric-to-chart mappings, configuring TLS on the OTLP receiver, or debugging OTLP ingestion issues with Netdata. Covers OTLP gRPC ingestion for metrics (v2.7.0+) and logs (v2.9.0+). Traces are not yet supported.
greptimedb-development-docker-image
Builds a development-only GreptimeDB Docker image from a local debug binary for local-cluster testing, and optionally pushes it to a development registry. Use when the user asks to package, build, tag, publish, or cross-build a non-release GreptimeDB or GreptimeDB Enterprise image for debugging.
greptimedb-fuzz-ci-failure-investigation
Investigate a failed GreptimeDB fuzz CI target link by downloading GitHub Actions job logs plus fuzz artifacts such as kind logs, monitor dumps, and CSV dumps, then correlate the failure with local GreptimeDB source code. Use when the user provides a failed fuzz CI target/job URL or asks to diagnose GreptimeDB fuzz CI…
greptimedb-release-note
Generate a GreptimeDB release changelog with git cliff (correct range, subtract already-released patch PRs, rebuild contributors, add human-curated highlights), output to a file, and prepare the docs-repo blog PR. Use when asked to write/generate a GreptimeDB release note or changelog.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).