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/notysoty/openagentskills/stack-trace-analyzernpx skills add Notysoty/openagentskills --skill stack-trace-analyzergit clone --depth 1 https://github.com/Notysoty/openagentskillsWhat 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.00024 | $0.01515 |
| Opus 5 | $0.00012 | $0.00758 |
| Sonnet 5 | $0.00005 | $0.00303 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
Stack Trace Analyzer 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 3d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Trace Analyzer
What this skill does
This skill directs the agent to read a stack trace, identify which frame is the true origin of the bug (not just where the error was thrown), explain what each relevant frame means in plain English, diagnose the root cause, and propose 2–3 concrete fixes ranked by likelihood. It works with JavaScript, TypeScript, Python, Java, Go, Rust, and most other common stack trace formats.
Use this when you have a crash report, a CI failure, or a wall of red text in your terminal and you want to understand it fast.
How to use
Claude Code / Cline
Copy this file to .agents/skills/stack-trace-analyzer/SKILL.md in your project root.
Then paste the stack trace and ask:
- "Analyze this stack trace using the Stack Trace Analyzer skill."
- "Use the Stack Trace Analyzer skill — what went wrong and how do I fix it?"
Include any relevant context: the action that triggered the error, environment details (Node version, browser, OS), and any recent code changes.
Cursor
Add the "Prompt / Instructions" section below to your .cursorrules file. Then paste the stack trace into the chat.
Codex
Paste the full stack trace and the relevant source files into the chat, then include the instructions below. Codex benefits from seeing the actual source code so it can match line numbers to real code.
The Prompt / Instructions for the Agent
When given a stack trace, follow these steps:
-
Identify the language and runtime from the trace format (Node.js, Python, JVM, Go panic, Rust panic, browser, etc.). Note the runtime version if visible.
-
Parse the error header. Extract:
- Error type (e.g.,
TypeError,NullPointerException,panic,KeyError) - Error message (the human-readable description)
- Any error codes or HTTP status codes present
- Error type (e.g.,
-
Walk the stack frames top-to-bottom. For each frame that belongs to application code (not a framework or standard library):
- State what the function does in plain English
- Note the file path and line number
- Explain why that frame is on the call stack (what called it)
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.
- 3d ago First seen · 147 lines · 24 tokens per session scan A ced6a08a5865
Stack Trace Analyzer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 19d ago), licensed MIT. It adds 24 tokens to every session and 1,515 once invoked, about $0.0001 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
waku-computer-use
Control local Mac apps through Waku Computer Use for tasks that require reading or operating app UI. Prefer purpose-built connectors, APIs, or CLIs when available.
tui-screen
Create TUI screens, components, and views for the agents-in-a-box terminal UI. Use when building new ratatui components, adding panels, creating list views, or styling any terminal interface element. Provides color palette, component patterns, and quality checklist.
ship-it
End-to-end ship loop: atomic commits, PR, tiered review (lite|heavy), fix every finding, re-review until zero remain, then merge-commit. lite runs a single /review pass; heavy spins up a dynamic Workflow with diff-aware review personas plus a Codex cross-model peer. Use when Stevie says "/ship-it", "ship it", "ship…
tmux-ui-tripwire
Write or debug tmux-driven end-to-end TUI tests ("tripwires") for the ainb terminal app. Use when the user asks to "write a tmux test", "add a tripwire", "verify the TUI in tmux", "test feature X by pressing key Y", "validate plugin Z renders", or when editing any file under crates/ainb-core/tests/tripwire.rs.…
tmux-verify
The outer "is this TUI feature ACTUALLY done?" proof loop for the ainb terminal app. Use when the user asks to "verify the TUI is actually done", "prove this TUI feature works", "validate per tmux-verify", "vhs verify each journey", "frame-truth check the UI", "is the diff actually shown correctly", or to define the…
ainb-fleet:bridge
Native phone bridge — relay messages two-way between a chat channel (Telegram, Slack, and/or Discord) and your ainb sessions. Inbound chat messages route to a target session (by name: prefix, else a conductor- first default) and are delivered via tmux send-keys; the session's reply is captured from its JSONL…