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 VersoXBT/claude-initial-setup --skill error-tracinggit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/error-tracing)<a href="https://agentmods.dev/skills/versoxbt/claude-initial-setup/error-tracing"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/error-tracing/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/versoxbt/claude-initial-setup/error-tracing"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/error-tracing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00059 | $0.02143 |
| Opus 5 | $0.00030 | $0.01071 |
| Sonnet 5 | $0.00012 | $0.00429 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
error-tracing 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 7d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Tracing
Read stack traces and error chains to trace errors back to their root cause across synchronous, asynchronous, and distributed code paths.
When to Use
- An error or stack trace appears in console, logs, or test output
- The user shares an exception and needs help understanding it
- Debugging async errors with incomplete stack traces
- Setting up error boundaries in React or similar frameworks
- Mapping minified production errors back to source code
Core Patterns
Reading Stack Traces
Stack traces read from top to bottom. The top frame is where the error was thrown; the bottom frame is the entry point:
Error: Cannot read properties of undefined (reading 'email')
at formatUser (src/utils/format.ts:42:18) <-- ERROR THROWN HERE
at processUsers (src/services/user.ts:87:12) <-- Called formatUser
at handler (src/routes/users.ts:23:5) <-- Called processUsers
at Layer.handle (node_modules/express/lib/router/layer.js:95:5)
Reading strategy:
- Read the error message first — it often tells you exactly what is wrong
- Find the first frame in YOUR code (skip
node_modules) - Go to that file and line —
src/utils/format.ts:42 - Understand what variable is
undefinedand trace where it came from - Walk up the stack to find where the bad data originated
// The error says: Cannot read 'email' of undefined
// At format.ts:42: user.email — so `user` is undefined
// At user.ts:87: formatUser(users[i]) — so users[i] is undefined
// Root cause: array has gaps or index is out of bounds
Error Chains (Cause Property)
Wrap errors to add context while preserving the original cause:
// Build error chains with the cause option (ES2022)
async function createOrder(data: OrderInput): Promise<Order> {
let user: User;
try {
user = await fetchUser(data.userId);
} catch (error) {
throw new Error(`Failed to create order: user lookup failed`, {
cause: error,
});
}
try {
return await insertOrder(user, data);
} catch (error) {
throw new Error(`Failed to create order: database insert failed`, {
cause: error,
});
}
}
// Reading the error chain
function logErrorChain(error: Error): void {
let current: Error | undefined = error;
let depth = 0;
while (current) {
const indent = " ".repeat(depth);
console.error(`${indent}${current.message}`);
if (current.stack) {
console.error(`${indent}${current.stack.split("\n")[1]?.trim()}`);
}
current = current.cause instanceof Error ? current.cause : undefined;
depth++;
}
}
// Output:
// Failed to create order: database insert failed
// at createOrder (src/services/order.ts:18:11)
// ECONNREFUSED 127.0.0.1:5432
// at Connection.connect (node_modules/pg/lib/connection.js:45:9)
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.
- 7d ago First seen · 307 lines · 59 tokens per session scan A 6a87ffe79e89
error-tracing is a skill published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 2,143 once invoked, about $0.0003 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
learner
Post-debugging knowledge extraction — captures non-obvious, codebase-specific learnings that pass quality gates. Invoke after resolving tricky bugs or discovering surprising behavior.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
principle-attack-the-premise
Apply when two or more fixes that share one premise have failed the same gate. Take a census of which actors hold the imbalance before the next fix, then question the premise instead of writing another fix that assumes it.
decision-table
Use when the user wants a code-grounded decision table for current behavior, wants to compare current behavior against a plan or work item, or needs a control-flow artifact for recovery, retry, finalization, validation, state-machine, or review-heavy edge cases.
claude-md-drift-check
Use when detecting drift between CLAUDE.md (or AGENTS.md, the Codex CLI alias) / meta narrative and live repository state. Ten checks: absolute-path resolution, 01-projects/ count claims, issue-reference freshness, session-file existence, command-count sync, session-config-parity (mandatory template keys = error…
fix-bug
Run the Fix Validation pipeline to investigate, fix, and validate a bug. Ensures deterministic pipeline execution with IssueAnalyzer, FixWriter, TestWriter (conditional), TestAudit (conditional), and FixValidator stages.