Traceway is an OpenTelemetry-based observability platform that collects and connects logs, traces, metrics, session replay, exceptions, and related operational data. Teams use it to understand software behavior and investigate problems. Catalogue add-ons can support workflows around operating and monitoring Traceway.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tracewayapp/tracewaynpx agentmods add skills/tracewayapp/traceway/integration-testWrote 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/tracewayapp/traceway/integration-test)<a href="https://agentmods.dev/skills/tracewayapp/traceway/integration-test"><img src="https://agentmods.dev/badge/skills/tracewayapp/traceway/integration-test/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/tracewayapp/traceway/integration-test"><img src="https://agentmods.dev/badge/skills/tracewayapp/traceway/integration-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00090 | $0.02486 |
| Opus 5.5 | $0.00036 | $0.00994 |
| Sonnet 5.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 28d 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.
- 28d ago Changed 177245e0207a
- 1mo 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,728 stars, last pushed yesterday), licensed MIT. It adds 90 tokens to every session and 2,486 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
test-suite-architect
This skill should be used when establishing comprehensive QA testing processes for any software project. Use when creating test strategies, writing test cases following Google Testing Standards, executing test plans, tracking bugs with P0-P4 classification, calculating quality metrics, or generating progress reports.…
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, setting log or trace retention, or debugging OTLP ingestion issues with Netdata. Covers OTLP gRPC ingestion for metrics (v2.7.0+), logs (v2.9.0+, current storage schema…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.