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/tsmztech/claude-code-plugins/debug-lognpx skills add tsmztech/claude-code-plugins --skill debug-loggit clone --depth 1 https://github.com/tsmztech/claude-code-pluginsWhat 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.00103 | $0.02961 |
| Opus 5 | $0.00051 | $0.01481 |
| Sonnet 5 | $0.00021 | $0.00592 |
| Haiku 4.5 | $0.00010 | $0.00296 |
Grade A, and why
debug-log 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 yesterday.
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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Log Management
Manage Salesforce debug logs and trace flags. This skill provides four scripts for the full debugging lifecycle: enable logging, retrieve logs, analyze them, and clean up.
Prerequisites
You must be authenticated to a Salesforce org before managing debug logs. If not authenticated, run the authentication script first.
Authentication
If the user is not authenticated or gets an auth error, run the authentication script:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --status
To authenticate interactively (opens browser):
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias>
To authenticate to a sandbox:
node ${CLAUDE_PLUGIN_ROOT}/scripts/sf-auth.js --alias <alias> --instance-url https://test.salesforce.com
CRITICAL: User is Mandatory for Trace Flag Actions
When the user asks to set or remove a trace flag, you MUST know which Salesforce user to target. The scripts require either --username (exact username) or --name (search by name).
- If the user does not specify who to trace, ASK them before running the script.
- Do NOT assume the current authenticated user — always confirm explicitly.
- You can use
--namefor a friendlier search (e.g.,--name "John") which does exact match first, then partial (LIKE '%John%'). - If
--namereturns multiple matches, the script will list them and exit — ask the user to pick one, then re-run with--username.
Actions & Scripts
This skill provides four scripts, one for each debugging action.
1. Set User Trace Flag
Enable debug logging for a user by creating a debug level and trace flag. User is required.
node ${CLAUDE_PLUGIN_ROOT}/skills/debug-log/scripts/set-trace-flag.js --username <user> | --name <name> [options]
Options
| Option | Description |
|---|---|
--username, -u <username> |
Exact username of the user to trace (e.g., [email protected]). Required unless --name is provided. |
--name, -n <name> |
Search by user name — tries exact match first, then partial (LIKE). Required unless --username is provided. |
--level, -l <preset> |
Debug level preset: finest, debug, apex (default: debug) |
--duration, -d <minutes> |
Duration in minutes the trace flag stays active (default: 30, max: 1440) |
--log-type, -t <type> |
Log type: DEVELOPER_LOG or USER_DEBUG (default: DEVELOPER_LOG) |
--target-org, -o <alias> |
Target org alias or username |
--json |
Output raw JSON |
--help, -h |
Show help |
What ships with it
4 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.
- yesterday First seen · 270 lines · 103 tokens per session scan A f1371b880f82
debug-log is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 103 tokens to every session and 2,961 once invoked, about $0.0005 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…