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 ArabelaTso/Skills-4-SE --skill trace-collection-assistantgit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote 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/arabelatso/skills-4-se/trace-collection-assistant)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/trace-collection-assistant"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/trace-collection-assistant/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/arabelatso/skills-4-se/trace-collection-assistant"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/trace-collection-assistant.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Privilege Escalation · line 159 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 162 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00087 | $0.01240 |
| Opus 5 | $0.00044 | $0.00620 |
| Sonnet 5 | $0.00017 | $0.00248 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade A, and why
trace-collection-assistant 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 9d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trace Collection Assistant
Overview
This skill helps collect, normalize, and structure execution traces produced by instrumented programs (strace, ltrace), making them suitable for downstream analysis such as debugging, reproduction, or verification. It converts raw trace output into structured JSON format and provides tools for filtering, cleaning, and extracting relevant information.
Quick Start
Basic Workflow
- Parse raw traces - Convert strace/ltrace output to JSON
- Filter and clean - Remove noise and focus on relevant calls
- Extract debug info - Identify errors, file operations, network activity
Example: Debugging with strace
# 1. Capture trace
strace -o trace.txt python buggy_program.py
# 2. Parse to JSON
python scripts/parse_strace.py trace.txt -o trace.json --pretty
# 3. Extract errors
python scripts/extract_debug_info.py trace.json --category errors --pretty
# 4. Filter to relevant operations
python scripts/filter_trace.py trace.json --error-only --remove-noise -o filtered.json --pretty
Example: Analyzing library calls with ltrace
# 1. Capture trace
ltrace -o trace.txt ./program
# 2. Parse to JSON
python scripts/parse_ltrace.py trace.txt -o trace.json --pretty
# 3. Analyze specific functions
python scripts/filter_trace.py trace.json --include-calls "malloc,free,strlen" --pretty
Core Operations
1. Parsing Traces
Convert raw trace output to normalized JSON format.
For strace:
python scripts/parse_strace.py <input_file> [--output <output_file>] [--pretty]
For ltrace:
python scripts/parse_ltrace.py <input_file> [--output <output_file>] [--pretty]
Both parsers produce the same normalized JSON structure (see references/json_schema.md for details).
2. Filtering Traces
Remove noise and focus on relevant operations.
Common filtering operations:
# Show only errors
python scripts/filter_trace.py trace.json --error-only --pretty
# Remove common noise syscalls
python scripts/filter_trace.py trace.json --remove-noise --pretty
# Include specific calls
python scripts/filter_trace.py trace.json --include-calls "open,read,write,close" --pretty
# Exclude specific calls
python scripts/filter_trace.py trace.json --exclude-calls "gettimeofday,clock_gettime" --pretty
# Filter by argument pattern
python scripts/filter_trace.py trace.json --arg-pattern "config.json" --pretty
# Combine filters
python scripts/filter_trace.py trace.json --error-only --remove-noise --arg-pattern "/etc" -o filtered.json --pretty
What ships with it
8 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.
- assets/schema_template.json 3.1 KB
- references/analysis_guide.md 4.2 KB
- references/json_schema.md 2.2 KB
- references/trace_formats.md 2.5 KB
- scripts/extract_debug_info.py 6.4 KB runs code
- scripts/filter_trace.py 3.9 KB runs code
- scripts/parse_ltrace.py 3.2 KB runs code
- scripts/parse_strace.py 3.3 KB runs code
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.
- 9d ago First seen · 177 lines · 87 tokens per session scan A 1bcd61d785d6
trace-collection-assistant is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (252 stars, last pushed 22d ago), licensed Apache-2.0. It adds 87 tokens to every session and 1,240 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-09-03.
Other skills, from other repositories
702-technologies-wiremock
Use when you need framework-agnostic WireMock guidance — stub design, JSON or programmatic mappings, precise request matching, response bodies and faults, classpath fixtures, isolation and reset between tests, verification of calls, dynamic ports and base URLs, and avoiding flaky stubs — without choosing Spring Boot…
321-frameworks-spring-boot-testing-unit-tests
Use when you need to write unit tests for Spring Boot applications — including pure unit tests with @ExtendWith(MockitoExtension.class) for @Service/@Component, slice tests with @WebMvcTest and @MockitoBean for controllers, @JsonTest for JSON serialization, parameterized tests with @CsvSource/@MethodSource, test…
java-code-review
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.
flake-triage
Decide whether a preview the visual-diff bot flagged actually regressed or is simply nondeterministic, using a repeat-render oracle at a single commit. Use when a PR's preview diff reports a changed preview whose source the PR does not touch, or when a render, GIF or filmstrip is suspected of being unstable.
codex-qa
QA the omo Codex Light edition (lazycodex / packages/omo-codex) itself, in strict isolation so ONLY our plugin is exercised, never the user's real /.codex. The first-party method drives the real codex app-server against an isolated CODEXHOME plus a LOCAL mock model (no real API call), and proves a plugin hook fired by…
refactor-safely
Restructure existing code safely without changing externally observable behavior. Composes context, design, architecture, code quality, and testing guardrails into a characterization-first refactoring workflow. Use when the user says 'refactor this', 'clean this up', 'untangle this module', 'move this to the right…