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 josefbacik/systing --skill systing-tracegit clone --depth 1 https://github.com/josefbacik/systingWrote 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/josefbacik/systing/systing-trace)<a href="https://agentmods.dev/skills/josefbacik/systing/systing-trace"><img src="https://agentmods.dev/badge/skills/josefbacik/systing/systing-trace/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/josefbacik/systing/systing-trace"><img src="https://agentmods.dev/badge/skills/josefbacik/systing/systing-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 10 findings, 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 Privilege Escalation · line 12 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 19 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 25 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 30 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 35 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 66 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 71 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 163 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 170 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Privilege Escalation · line 166 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
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.00089 | $0.03182 |
| Opus 5 | $0.00044 | $0.01591 |
| Sonnet 5 | $0.00018 | $0.00636 |
| Haiku 4.5 | $0.00009 | $0.00318 |
Grade B, and why
systing-trace scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo systing --output trace.duckdb -- python3 myscript.py How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capturing a trace with systing
systing is a BPF-based Linux tracer. It captures scheduling events, IRQs, stack traces, network activity, memory events, syscalls, and more into a DuckDB database (or Perfetto trace) for later analysis.
Prerequisites
- Must run as root, or hold
CAP_BPF+CAP_PERFMON(CAP_SYS_ADMINalso works). Usesudo. - Output: prefer
--output foo.duckdbfor analysis with thesysting-analyzeMCP server. The default istrace.pb(Perfetto), so always pass--outputexplicitly when you want DuckDB.
Common invocations
Trace a command from start to finish
sudo systing --output trace.duckdb -- python3 myscript.py
Everything after -- is the command. Only the command, its threads, and children are traced.
Trace an existing PID for N seconds
sudo systing -p <PID> -d 10 --output trace.duckdb
Trace a cgroup
sudo systing -c /sys/fs/cgroup/my.slice -d 30 --output trace.duckdb
System-wide trace (no PID/cgroup filter)
sudo systing -d 5 --output trace.duckdb
-d 0 (the default) means "run until Ctrl-C, or until the -- command exits".
Recorders (what to capture)
List available recorders and their defaults:
systing --list-recorders
| Recorder | Default | Captures |
|---|---|---|
sched |
on | Scheduler events (context switches, wakeups, runqueue) |
irq |
on | IRQ and softirq events (irq_handler_*, softirq_*) |
cpu-stacks |
on | On-CPU perf stack samples |
sleep-stacks |
on | Uninterruptible sleep (D-state) stacks |
interruptible-stacks |
on | Interruptible sleep (S-state) stacks |
syscalls |
off | All syscall entry/exit (raw_syscalls:sys_enter/sys_exit) |
network |
off | Base network recorder: socket/TCP connection state tracking |
network-syscalls |
off | Network syscall-level tracing (send/recv bytes, buffer fill, stalls) — no per-packet probes |
network-packets |
off | Packet-level tracing (sendmsg, recvmsg, qdisc, drops, retransmits, RTT) |
memory |
off | RSS tracking, mmap/munmap/brk, page faults |
memory-alloc |
off | Heap allocator uprobes (malloc/calloc/realloc/free) with stacks |
markers |
off | Userspace marker events (faccessat2 with mode=-975) |
tpu |
off | TPU op-level profile via XLA runtime gRPC (port 8466) |
tpu-metrics |
off | TPU runtime metrics polling (port 8431, lightweight) |
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 · 193 lines · 89 tokens per session scan B 2dbb9b61345a
systing-trace is a skill published in the GitHub repository josefbacik/systing (176 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 3,182 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.