ODS is a system for turning a PC, Mac, or Linux computer into a private local AI server, meaning a machine that runs models and related AI services itself. It supports local model inference, chat, voice, agents, workflows, document retrieval, search, and image generation. The catalogue includes commands and an instruction for operating or configuring this system.
Borrowing it
Nothing to install: this file belongs to Osmantic/ODS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Osmantic/ODS/main/.claude/commands/log-fix.mdgit clone --depth 1 https://github.com/Osmantic/ODSWrote 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/commands/osmantic/ods/log-fix)<a href="https://agentmods.dev/commands/osmantic/ods/log-fix"><img src="https://agentmods.dev/badge/commands/osmantic/ods/log-fix/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/commands/osmantic/ods/log-fix"><img src="https://agentmods.dev/badge/commands/osmantic/ods/log-fix.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.00000 | $0.03995 |
| Opus 5.5 | $0.00000 | $0.01598 |
| Sonnet 5.5 | $0.00000 | $0.00799 |
| Haiku 4.5 | $0.00000 | $0.00400 |
Grade A, and why
log-fix 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 2mo 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 -sf http://127.0.0.1:8080/health && echo "LLM server: HEALTHY" || echo "LLM server: UNREACHABLE" How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log-Fix: Iterative Bug Fixing from Log Analysis
Analyze logs from Docker containers, installer runs, and service health checks. Identify errors, perform root cause analysis, and interactively fix issues with user approval.
"Logs tell stories. This skill reads them and writes the fixes."
Arguments
$ARGUMENTS- Optional filters and configuration:--time <duration>- Time range:1h,30m,1d,7d(default:1h)--source <source>- Log source:docker,installer,api,all(default:all)--level <level>- Minimum severity:ERROR,WARNING,all(default:ERROR)--service <name>- Filter by service name (e.g.,ods-llama-server,ods-open-webui,ods-dashboard)
Phase 0: Log Source Discovery
Detect all available log sources before analysis.
0.1 Check Docker Compose Logs
# Find the resolved compose stack
COMPOSE_FILES=""
if [ -f "ods/docker-compose.base.yml" ]; then
COMPOSE_FILES="-f ods/docker-compose.base.yml"
for overlay in ods/docker-compose.{amd,nvidia,apple}.yml; do
[ -f "$overlay" ] && COMPOSE_FILES="$COMPOSE_FILES -f $overlay"
done
fi
# Check running containers
if [ -n "$COMPOSE_FILES" ]; then
docker compose $COMPOSE_FILES ps --format "table {{.Name}}\t{{.Status}}" || echo "Docker not running"
else
echo "No compose files found"
fi
0.2 Check Installer Logs
INSTALL_LOG="$HOME/.ods/install.log"
if [ -f "$INSTALL_LOG" ]; then
INSTALL_SIZE=$(du -h "$INSTALL_LOG" | cut -f1)
INSTALL_LINES=$(wc -l < "$INSTALL_LOG")
echo "Installer log: $INSTALL_LOG ($INSTALL_SIZE, $INSTALL_LINES lines)"
else
echo "Installer log: NOT FOUND at $INSTALL_LOG"
fi
0.3 Check Service Health Endpoints
# LLM server health
curl -sf http://127.0.0.1:8080/health && echo "LLM server: HEALTHY" || echo "LLM server: UNREACHABLE"
# Dashboard API health
curl -sf http://127.0.0.1:3001/health && echo "Dashboard API: HEALTHY" || echo "Dashboard API: UNREACHABLE"
# Open WebUI
curl -sf http://127.0.0.1:3000 && echo "Open WebUI: HEALTHY" || echo "Open WebUI: UNREACHABLE"
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.
- 2mo ago First seen · 489 lines · 0 tokens per session scan A a04d14e12dc2
log-fix is a command published in the GitHub repository Osmantic/ODS (7,712 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,995 tokens. 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-30.
Other commands, from other repositories
fix-issue
Investigate and fix an issue.
fire-resurrect
Autonomous Resurrection Mode — reverse-engineer intent from messy code, then rebuild clean from scratch.
check
View the latest screenshot from /Pictures/Screenshots.
fire-reflect
After any failure (debug resolution, test failure, approach rotation, stalled loop), capture what was tried, why it failed, and what actually worked as a persistent reflection. Future sessions search these before investigating.
fire-verify-uat
Conversational User Acceptance Testing with automatic parallel diagnosis on failures.
code-review
Code review a pull request.