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 skills add baphuongna/pi-crew --skill event-log-tracinggit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/event-log-tracing)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/event-log-tracing"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/event-log-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/baphuongna/pi-crew/event-log-tracing"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/event-log-tracing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 313 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00045 | $0.03092 |
| Opus 5.5 | $0.00018 | $0.01237 |
| Sonnet 5.5 | $0.00009 | $0.00618 |
| Haiku 4.5 | $0.00005 | $0.00309 |
Grade A, and why
event-log-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 2mo 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
event-log-tracing
Every pi-crew run writes a persistent event log at .crew/state/runs/<runId>/events.jsonl. Events are the primary evidence for understanding what happened — especially when workers crash, agents get stuck, or runs become orphaned.
Event Format
Every event is a JSON object on one line:
{
"time": "2026-05-14T10:27:52.000Z",
"type": "worker.spawned",
"runId": "team_20260514092752_218fe358085d7115",
"taskId": "01_explore",
"message": "Worker spawned: pid 12345",
"data": { "pid": 12345, "role": "explorer" },
"metadata": {
"seq": 42,
"provenance": "team_runner",
"fingerprint": "a1b2c3d4e5f6g7h8"
}
}
Required fields: time, type, runId
Optional fields: taskId, message, data, metadata
Metadata auto-populated: seq (line number), provenance (who wrote it), fingerprint (for terminal events)
Event Taxonomy
Worker Lifecycle Events (from child-pi.ts via onLifecycleEvent callback)
| Event | When | Data |
|---|---|---|
worker.spawned |
Child process starts with a PID | {pid, cwd} |
worker.spawn_error |
Spawn failed (no PID, binary not found, permission denied) | {pid?, error} |
worker.response_timeout |
No stdout for responseTimeoutMs (default 5 min) |
{pid, error} |
worker.final_drain |
Child finished but lingered — SIGTERM sent | {pid} |
worker.hard_kill |
Child still alive after hardKillMs — SIGKILL sent |
{pid} |
worker.exit |
Process exited (before close) | {pid, exitCode} |
worker.close |
stdio fully closed | {pid, exitCode} |
Tracing worker crashes:
worker.spawnedfollowed byworker.exitwith non-zero code → worker crashedworker.spawnedfollowed immediately byworker.spawn_error→ spawn failedworker.spawnedfollowed byworker.response_timeout→ worker hungworker.spawnedfollowed byworker.final_drain→ worker lingered but completedworker.spawnedfollowed byworker.hard_kill→ worker had to be forcibly killed
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.
- 2mo ago Changed · +3 lines · +27 tokens per session c69af39dbce7
- 2mo ago First seen · 314 lines · 18 tokens per session scan A 46bb7bfcaf54
event-log-tracing is a skill published in the GitHub repository baphuongna/pi-crew (57 stars, last pushed 7d ago), licensed MIT. It adds 45 tokens to every session and 3,092 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-08-30.
event-log-tracing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| event-log-tracingbaphuongna/pi-crew | Skill | 57 | 7d ago | MIT | A | 45 | Claude Code, Codex |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | today | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | today | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 326 | today | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | today | Apache-2.0 | A | 15 | Claude Code, Codex |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |
| triaging-web-analytics-supportPostHog/posthog | Skill | 41k | today | none | A | 151 | Claude Code, Codex |