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/socketdev/sauce/updating-xportnpx skills add SocketDev/sauce --skill updating-xportgit clone --depth 1 https://github.com/SocketDev/sauceWhat 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.00050 | $0.02421 |
| Opus 5 | $0.00025 | $0.01210 |
| Sonnet 5 | $0.00010 | $0.00484 |
| Haiku 4.5 | $0.00005 | $0.00242 |
Grade A, and why
updating-xport scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `<prefix>_1_2_3` (underscore style; curl, liburing) How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
updating-xport
The harness at scripts/xport.mts emits JSON reports with severity ∈ {ok, drift, error} per row. This skill consumes that JSON.
Per-kind action policy:
| Kind | Drift signal | Action |
|---|---|---|
version-pin |
Upstream commits on default ref since pinned SHA | Auto-bump per upgrade_policy: track-latest → advance to latest stable tag; major-gate → advance patch/minor only; locked → advisory only |
file-fork |
Upstream file changed since forked_at_sha |
Advisory - note in PR body; do NOT auto-merge (forks carry local deltas that need human review) |
feature-parity |
Parity score below criticality/10 floor |
Advisory - note in PR body; human decides implement vs downgrade criticality |
spec-conformance |
Spec submodule moved | Advisory - note in PR body; human decides whether to bump spec_version |
lang-parity |
Port divergence / rejected anti-pattern reintroduced |
Advisory - note in PR body; humans fix the port or update the manifest |
The common rule: version-pin is mechanical (safe to auto-apply with track-latest/major-gate policies); everything else is advisory (upstream semantics and local deltas matter, humans decide).
Forbidden:
- Never auto-edit
file-fork,feature-parity,spec-conformance, orlang-parityrows' tracked state - Never bump a
lockedversion-pin without human approval - Never skip the tag-stability filter
- Never use
npx,pnpm dlx,yarn dlx- usepnpm execorpnpm run
CI mode (CI=true or GITHUB_ACTIONS): skip per-row test validation (workflow validates at the end); emit advisory summary to $GITHUB_OUTPUT when present.
Interactive mode (default): validate each auto-bump with pnpm test before committing the next.
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.
- 2d ago First seen · 224 lines · 50 tokens per session scan A a60c6fb86913
updating-xport is a skill published in the GitHub repository SocketDev/sauce (2 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 2,421 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…