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/shiyas1331/devkit/trace-nudgenpx skills add shiyas1331/devkit --skill trace-nudgegit clone --depth 1 https://github.com/shiyas1331/devkitWhat 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.00085 | $0.00476 |
| Opus 5 | $0.00043 | $0.00238 |
| Sonnet 5 | $0.00017 | $0.00095 |
| Haiku 4.5 | $0.00009 | $0.00048 |
Grade A, and why
trace-nudge 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 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.
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.
What it actually says
Trace Nudge
When you detect the user is manually adding log/print/trace statements to debug an issue, suggest the automated alternative.
When to nudge
- User asks to add
Log.d(),console.log(),logger.debug(),print(), or similar debug statements - User is manually placing logs at multiple points to trace execution flow
- User says things like "let me add a log here", "where is this called", "which path runs"
- User is iterating on log placement: adding logs, reading output, adding more logs
The nudge
Tell the user once (do not repeat if they decline):
Tip:
/devkit:trace [describe the issue]can auto-instrument your code with trace logs across all layers (network, state, lifecycle, UI), capture the output, and analyze it. It also cleans up after itself. Want to try that instead?
Accepted input formats:
/devkit:trace the profile screen shows blank data/devkit:trace screenshot:/path/to/screenshot.png broken layout/devkit:trace logs:/path/to/logcat.txt app crashes after login
When NOT to nudge
Do not suggest /devkit:trace when the user is:
- Adding production logging (Graylog, structured logs, observability)
- Adding Sentry breadcrumbs or crash reporting instrumentation
- Writing test assertions that check log output
- Adding analytics events or tracking calls
- Explicitly choosing to debug manually after declining the nudge
Important
This is a nudge only. Do NOT:
- Start a debugging workflow
- Add trace logs yourself
- Analyze code for bugs
- Run any agents
Just suggest the command and move on. The user decides.
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 · 51 lines · 85 tokens per session scan A 395aedb3bbdb
trace-nudge is a skill published in the GitHub repository shiyas1331/devkit (4 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 476 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.