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/aksika/abtars/troubleshootingnpx 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.svg" alt="Measured on agentmods" 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.00011 | $0.00420 |
| Opus 5 | $0.00005 | $0.00210 |
| Sonnet 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 6d 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.
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 'extracted', COUNT(*) FROM extracted_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.
- 6d ago First seen · 46 lines · 11 tokens per session scan A 721546f34c8a
troubleshooting is a skill published in the GitHub repository aksika/abtars (9 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 420 once invoked, about $0.0001 per session on Opus 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
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
observability
Use when you say query agent logs, find slow tool calls, or show agent errors. Query and analyze agent JSONL event logs for debugging, performance analysis, and decision tracing.
validation-authority
Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.
ai-agents-config-catalog
Catalog of every configuration axis in this repo, env vars, commit markers, frontmatter keys, QA skip verdicts, and escape hatches, each with its enforcement point and abuse story, plus the checklist for adding a new flag safely. Use when you say what does a skip flag do, list escape hatches, can I skip this gate, add…