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/zxfccmm4/obsidian-opencode-knowledge/opencli-autofixnpx skills add zxfccmm4/Obsidian-OpenCode-Knowledge --skill opencli-autofixgit clone --depth 1 https://github.com/zxfccmm4/Obsidian-OpenCode-KnowledgeWrote 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/zxfccmm4/obsidian-opencode-knowledge/opencli-autofix)<a href="https://agentmods.dev/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-autofix"><img src="https://agentmods.dev/badge/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-autofix.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 | $0.00067 | $0.00738 |
| Opus 5 | $0.00034 | $0.00369 |
| Sonnet 5 | $0.00013 | $0.00148 |
| Haiku 4.5 | $0.00007 | $0.00074 |
Grade A, and why
opencli-autofix 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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCLI AutoFix — Automatic Adapter Self-Repair
When an opencli command fails because a website changed its DOM, API, or response schema, automatically diagnose, fix the adapter, and retry.
Safety Boundaries
AUTH_REQUIRED(exit code 77) — STOP. Tell user to log into the site in Chrome.BROWSER_CONNECT(exit code 69) — STOP. Tell user to runopencli doctor.- CAPTCHA / rate limiting — STOP. Not an adapter issue.
- Only modify
RepairContext.adapter.sourcePath— never modifysrc/,extension/,tests/ - Max 3 repair rounds per failure
Step 1: Collect Diagnostic Context
OPENCLI_DIAGNOSTIC=1 opencli <site> <command> [args...] 2>diagnostic.json
Step 2: Analyze the Failure
| Error Code | Likely Cause | Repair Strategy |
|---|---|---|
| SELECTOR | DOM restructured | Explore current DOM → find new selector |
| EMPTY_RESULT | API response schema changed | Check network → find new response path |
| API_ERROR | Endpoint URL changed | Discover new API via network intercept |
| AUTH_REQUIRED | Login flow changed, cookies expired | STOP — tell user to log in |
| TIMEOUT | Page loads differently | Add/update wait conditions |
| PAGE_CHANGED | Major redesign | May need full adapter rewrite |
Step 3: Explore the Current Website
Use opencli browser to inspect the live website. Never use the broken adapter.
# DOM changed
opencli browser open https://example.com/target-page && opencli browser state
# API changed
opencli browser open https://example.com/target-page && opencli browser network
Step 4: Patch the Adapter
Read the adapter source file at RepairContext.adapter.sourcePath and make targeted fixes.
Common Fixes
Selector update:
// Before: page.evaluate('document.querySelector(".old-class")...')
// After: page.evaluate('document.querySelector(".new-class")...')
API endpoint change:
// Before: fetch('/api/v1/old-endpoint')
// After: fetch('/api/v2/new-endpoint')
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.
- 4d ago First seen · 91 lines · 67 tokens per session scan A 4b3e6b2eb518
opencli-autofix is a skill published in the GitHub repository zxfccmm4/Obsidian-OpenCode-Knowledge (291 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 738 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-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.
traceway-setup
Analyze and instrument repositories for Traceway observability. Use when the user wants to plan, add, migrate, or verify Traceway or OpenTelemetry monitoring for backend, browser, full-stack, mobile or iOS, or AI-agent software, including project topology and user-approved setup-plan creation. Backends use OTLP/HTTP…