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/baphuongna/pi-crew/runtime-state-readernpx skills add baphuongna/pi-crew --skill runtime-state-readergit 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/runtime-state-reader)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/runtime-state-reader"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/runtime-state-reader.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00563 |
| Opus 5 | $0.00008 | $0.00282 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
runtime-state-reader 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
runtime-state-reader
Use this skill when debugging or auditing a pi-crew run.
Source patterns distilled
src/state/types.ts,src/state/contracts.ts,src/state/state-store.tssrc/state/event-log.ts,src/state/artifact-store.ts,src/runtime/crew-agent-records.tssrc/extension/run-index.ts,src/extension/team-tool/status.ts,src/extension/team-tool/inspect.ts
Rules
- Prefer exported state APIs over direct file parsing:
loadRunManifestById(cwd, runId), run index/list helpers, event readers, and agent readers. - Treat state as append-mostly/durable. For review and debugging, do not mutate manifests/tasks/events.
- Validate run IDs and path-derived IDs; never concatenate untrusted path segments outside state helpers.
- Read events as JSONL; expect partial/corrupt trailing lines in crash scenarios and handle gracefully.
- Check status contracts before inferring behavior: terminal vs active run/task statuses matter.
- Agent aggregate records (
agents.json) and per-agent status files can disagree briefly; prefer the latest loaded run state plus event log for final conclusions. - Include exact paths inspected and distinguish direct evidence from inference.
Common inspection order
- Load manifest/tasks.
- Check run/task statuses and timestamps.
- Read recent events.
- Read agent records and per-agent output/status if needed.
- Inspect artifacts/diagnostics only through contained paths.
- Report root cause and smallest safe remediation.
Enforcement — Runtime State Reader Gate
Before inspecting or reporting on run state, verify:
- Using exported state APIs (not direct file parsing where helpers exist)
- State treated as append-mostly (no mutations during review/debugging)
- runId validated before use (no untrusted path concatenation)
- Corrupt JSONL handled gracefully (skip malformed lines)
- Terminal vs active statuses distinguished (critical for conclusions)
- Exact paths inspected reported with direct evidence vs inference labeled
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.
- 3d ago First seen · 64 lines · 15 tokens per session scan A 44018d512ae2
runtime-state-reader is a skill published in the GitHub repository baphuongna/pi-crew (50 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 563 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…