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 aksika/abtars --skill troubleshootinggit clone --depth 1 https://github.com/aksika/abtarsWrote 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/aksika/abtars/troubleshooting)<a href="https://agentmods.dev/skills/aksika/abtars/troubleshooting"><img src="https://agentmods.dev/badge/skills/aksika/abtars/troubleshooting/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/aksika/abtars/troubleshooting"><img src="https://agentmods.dev/badge/skills/aksika/abtars/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 44 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00011 | $0.00421 |
| Opus 5.5 | $0.00004 | $0.00168 |
| Sonnet 5.5 | $0.00002 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
troubleshooting 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 today.
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.
curl -s "https://api.telegram.org/bot${TOKEN}/getMe" | jq .ok What it actually says
Troubleshooting
Bridge process
ps aux | grep 'dist/main.js' | grep -v grep
tail -c 20000 ~/.abtars/logs/bridge.log | sed 's/2026-/\n2026-/g' | grep -v 'memory-db.*Database initialized' | tail -50
Orphaned processes
ps aux | grep 'kiro-cli.*acp' | grep -v grep | awk '{print $2, $9, $11}' | while read pid start cmd; do
ppid=$(awk '/PPid/{print $2}' /proc/$pid/status 2>/dev/null)
bridge=$(ps -p $ppid -o cmd= 2>/dev/null)
[[ "$bridge" != *"dist/main.js"* ]] && echo "ORPHAN: pid=$pid ppid=$ppid"
done
Browser agent
Memory DB
sqlite3 ~/.abtars/memory/memory.db "SELECT 'messages', COUNT(*) FROM messages UNION ALL SELECT 'durables', COUNT(*) FROM long_term_memories;"
timeout 3 sqlite3 ~/.abtars/memory/memory.db "SELECT COUNT(*) FROM messages;" && echo "DB OK" || echo "DB LOCKED"
Pending tasks
cat ~/.abtars/memory/cron.json 2>/dev/null | jq '.[] | select(.fired == false)'
cat ~/.abtars/memory/pending_browse.json 2>/dev/null
cat ~/.abtars/memory/pending_reminders.json 2>/dev/null
Telegram connectivity
TOKEN=$(cat ~/.abtars/secret/TELEGRAM_BOT_TOKEN)
curl -s "https://api.telegram.org/bot${TOKEN}/getMe" | jq .ok
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.
- today Changed ead7dc7affa8
- 1mo ago First seen · 46 lines · 11 tokens per session scan A 721546f34c8a
troubleshooting is a skill published in the GitHub repository aksika/abtars (10 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 421 once invoked, about $0.0000 per session on Opus 5.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
performance-profiling
CPU, memory, network bottleneck analysis — systematic performance investigation.
power-bi-performance-troubleshooting
Systematic Power BI performance troubleshooting prompt for identifying, diagnosing, and resolving performance issues in Power BI models, reports, and queries.
tlamatini-flw-doctor
Validate a .flw workflow file: check connection topology, terminal agents, Parametrizer single-lane queue, missing connectors, dangling targetagents.
refactor
Systematic code refactoring to improve maintainability without changing behavior. Use when asked to "refactor this", "clean up this code", "improve code quality", "simplify this", "reduce complexity", or "eliminate code smells". Always preserves existing behavior.
refactoring-patterns
Safe transformations — same behavior, better structure.
extension-audit-methodology
Systematic 5-dimension audit framework for VS Code extensions — debug hygiene, dead code, performance, menu validation, dependency cleanup.