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/understudylabs/understudy-agent-tools/ingest-tracesnpx skills add understudylabs/understudy-agent-tools --skill ingest-tracesgit clone --depth 1 https://github.com/understudylabs/understudy-agent-toolsWrote 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/understudylabs/understudy-agent-tools/ingest-traces)<a href="https://agentmods.dev/skills/understudylabs/understudy-agent-tools/ingest-traces"><img src="https://agentmods.dev/badge/skills/understudylabs/understudy-agent-tools/ingest-traces.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.00080 | $0.02496 |
| Opus 5 | $0.00040 | $0.01248 |
| Sonnet 5 | $0.00016 | $0.00499 |
| Haiku 4.5 | $0.00008 | $0.00250 |
Grade A, and why
ingest-traces 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 4d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest Traces
../capture-evidence/SKILL.md assumes a local
harness can be attached and run. Many workloads arrive the other way around:
the traces already exist — in an object-store bucket, a provider log export,
or an Understudy gateway capture export — and the job is to get them into
local evidence artifacts without leaking anything. This worker does that
transformation: local source → normalized captures → source-history DAG →
machine-proposed benchmark → human judgment, all on the local machine.
When the developer has only a hosted trace_id, acquire its private local
files first with ../export-trace/SKILL.md. This
skill begins after capture files exist locally and does not recreate the hosted
trace-to-request lookup.
OSS filesystem boundary
This public skill starts with files already present in .understudy/captures/
or another explicitly supplied local directory. It never invokes a privileged
administrative surface, changes tenant membership, or embeds a vendor-specific
downloader. Acquisition is a separate producer; this skill owns processing.
Safety Gates
- Raw bodies never leave the source files. Manifests reference traces by path/key and carry counts, schemas, and hashes — never prompt text, completions, or tool payloads. Downstream tools fetch bodies from disk at runtime.
- No identifiers in artifacts. Bucket names, org/account ids, and customer
identifiers stay in local credentials/config; manifests use relative keys
only. Every manifest records
privacy.local_only: trueandprivacy.upload_performed: false, and is itself review-gated before any external reference. - Downloading from a customer-controlled bucket is a read of customer data —
confirm the developer is authorized for that source before pulling, and
keep the pulled files under
.understudy/(gitignored). - Do not upload source files, prompts, traces, outputs, or datasets unless the developer explicitly approves that exact action in the current thread.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 211 lines · 80 tokens per session scan A dd1b5a70f890
ingest-traces is a skill published in the GitHub repository understudylabs/understudy-agent-tools (16 stars, last pushed 2d ago), licensed MIT. It adds 80 tokens to every session and 2,496 once invoked, about $0.0004 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…