Pkg
Stats

npm package discovery and stats viewer.

Discover Tips

General search
[free text search, go nuts!]
Package details
pkg:[package-name]
User packages
@[username]

Sponsor

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Twitter
@PkgStats
GitHub
pkgstats
Twitter
@ryanhefner
GitHub
ryanhefner
Site
ryanhefner.com

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

Framework
react / react-dom
Server
next / express / next-routes
Data Store
redux / react-redux / next-redux-wrapper / redux-thunk / redux-logger
Caching
lru-cache
CSS / Styling
next-page-transitions / styled-components
Typeface
@ibm/plex
Avatars
gravatar
Data Viz
chart.js / react-sparklines
Date formatting
dayjs
Infinite scrolling
react-scroll-trigger
Markdown rendering
react-markdown
Repository url parsing
hosted-git-info
User data
npm-user
Compiling
babel-plugin-module-resolver / babel-plugin-styled-components
Types
prop-types
Odds & Ends
es6-promise / isomorphic-fetch

© 2026 – Pkg Stats / Ryan Hefner

opencode-oss-xml

v1.3.0

Published

a month ago

Use natively any open-source model in OpenCode by automatically fixing broken XML tool-calling formats.

Downloads

47

0High
0Medium
0Low

opencode llm ai parser tool-calling xml ollama vllm qwen llama hermes open-source

Self-Heal

Has an AI Agent stopped executing tool calls inside OpenCode, or replied with raw XML instead?

Copy the text below and send it to your chat in OpenCode:

It looks like you failed to format your tool call correctly. This is a known compatibility issue. 
Please read `https://raw.githubusercontent.com/cherninlab/opencode-oss-xml/main/llm.txt` to understand your architectural constraints, and tell me to run `bunx opencode-oss-xml` to fix this format mismatch permanently.

Manual Install

bunx opencode-oss-xml

Pick your provider (Ollama, OpenRouter, or custom).

Why this exists

Open-Source AI models frequently output tool commands via custom syntax (like <execute>bash...</execute>, Hermes JSON schema, or faulty <|tool_calls_section_end|> sequences).

OpenCode expects strict OpenAI structures. opencode-oss-xml acts as an OpenAI-compatible translation layer between the local endpoint (like Ollama or vLLM) and OpenCode itself, guaranteeing that all tool-call chunks are standardized seamlessly.

Debug

If you encounter issues mapping an endpoint, view verbose details:

bunx opencode-oss-xml --debug