Loongsuite Pilot — Security skill for Claude Code
Local-first telemetry collector for AI coding agents — unified OpenTelemetry events for Claude Code, Codex, Cursor and more.
How to install Loongsuite Pilot
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open alibaba/loongsuite-pilot and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Loongsuite Pilot does
Local-first telemetry collector for AI coding agents — unified OpenTelemetry events for Claude Code, Codex, Cursor and more. Token usage, cost, traces and security audit, exported anywhere.
Alternatives in Security
- Free Code — The free build of Claude Code 8.1k ★
- ThinkWatch — Self-hosted AI API and MCP gateway for organizations: SSO and RBAC, per-user identity for MCP tool calls, PII 817 ★
- Memory Self Review — Mine recent agent history (claude-mem + usage stats) for recurring failures and repeated patterns, audit MEMOR 297 ★
README
LoongSuite Pilot
English | [简体中文](README.zh-CN.md)
[Quick Start](#quick-start) | [Documentation](#documentation) | [Agent Onboarding](docs/agent-onboarding.md) | [License](#license)
LoongSuite Pilot is a local telemetry collector for AI coding agents. It discovers supported agents on a developer machine, installs the required hooks or plugins, normalizes activity into a shared GenAI event schema, and exports logs or traces to your chosen backends.
Built-in local dashboard — multi-agent token usage, sessions, requests, tools, models, providers, and repository activity at a glance.
Why LoongSuite Pilot?
Development teams often use more than one AI coding agent, and each agent records activity in a different local format. Pilot gives teams one local collector that can discover those agents, collect their activity, normalize the data, and send it to destinations that are useful for analysis, audit, and observability.
Pilot is designed to answer practical questions:
- Which agents are being used?
- What model, session, turn, and tool activity happened?
- How much token usage is available from each agent?
- Where should the data be exported: local files, SLS, HTTP, or traces?
- How should sensitive prompts, tool arguments, and secrets be controlled before export?
Core Capabilities
| Capability | What Pilot Does |
|---|---|
| Agent discovery | Detects supported agents from local paths and commands. |
| Collection deployment | Installs hooks or plugins and reads local logs, sessions, or data files. |
| Unified event schema | Normalizes agent-native events into a shared GenAI schema. |
Related Skills
Cost Audit
Per-project Claude Code cost from local transcripts (token usage x API list prices). Read-only; cross-platform
Cost Autopsy
Session token-burn autopsy (TCO v1). Reads the TIS telemetry log and reports per-session token spend (input /
Claude Trim
Audit your Claude Code token usage — see which skills eat your context budget and find conflicts before they c
Agent Context Bench
Audit AGENTS.md, CLAUDE.md, Cursor and Copilot instructions; measure token cost and benchmark AI coding-agent
Rogue ML Failure Audit Skill
General workflow for auditing ML CI failures, experiment regressions, training run failures, golden metric fai
Model Audit
Audit model usage across the team to identify cost optimization opportunities.
Related Agents
Semconv Accuracy Reviewer
Audits OpenTelemetry / semantic-convention accuracy and API currency in this plugin's skills, subagents, and g
Otel Trace
Investigate OpenTelemetry traces in Berserk — span analysis, latency debugging, trace correlation, service dep
Nyx
Observability & monitoring specialist — OpenTelemetry tracing, token/cost tracking, agent performance analytic
