Open-Source Traction Analysis with GitHub Repo Stats in OpenClaw

OpenClaw is a solid local AI agent, but it can’t look up live data from GitHub on its own. When you ask about a project’s popularity or maintenance status, it’s limited to whatever it learned during training. AgentPatch’s github-repo-stats tool gives it direct access to stars, forks, open issues, languages, topics, and recent activity for any public repo.

Why This Matters

Whether you’re scouting projects for a tech stack decision, tracking the traction of a competitor’s open-source tool, or just curious whether a library is still maintained, the answer lives on GitHub. Manually checking each repo works for one or two, but if you’re comparing a handful of options across multiple criteria, it gets old fast.

With github-repo-stats connected through AgentPatch, your OpenClaw bot can fetch this data on demand. Ask a question in Telegram or Discord and get back real numbers instead of vague impressions.

Setup

The AgentPatch CLI is designed for AI agents to use via shell access. Install it, and your agent can discover and invoke any tool on the marketplace.

Install (zero dependencies, Python 3.10+):

pip install agentpatch

Set your API key:

export AGENTPATCH_API_KEY=your_api_key

Example commands your agent will use:

ap search "web search"
ap run google-search --input '{"query": "test"}'

Get your API key from the AgentPatch dashboard.

Install the AgentPatch skill from ClawHub — it teaches OpenClaw when to use AgentPatch and how to use the CLI:

clawhub install agentpatch

MCP Server (Alternative)

If you prefer raw MCP tool access instead of the skill, add AgentPatch to ~/.openclaw/openclaw.json:

{
  "mcp": {
    "servers": {
      "agentpatch": {
        "transport": "streamable-http",
        "url": "https://agentpatch.ai/mcp",
        "headers": {
          "Authorization": "Bearer YOUR_API_KEY"
        }
      }
    }
  }
}

Replace YOUR_API_KEY with your actual key from the AgentPatch dashboard. Restart OpenClaw and it discovers all AgentPatch tools automatically.

Example

You’re chatting with your OpenClaw bot and want to understand the current landscape of JavaScript runtime alternatives:

“Get the GitHub stats for denoland/deno and nicolo-ribaudo/bun. Which has more momentum right now?”

Your bot fetches stats for both:

Fetching GitHub stats for denoland/deno...
Fetching GitHub stats for oven-sh/bun...

denoland/deno:
- 98,500 stars, 5,400 forks
- 1,890 open issues
- Last commit: 6 hours ago
- Primary language: Rust
- Topics: javascript, typescript, runtime, deno

oven-sh/bun:
- 75,200 stars, 2,800 forks
- 1,420 open issues
- Last commit: 4 hours ago
- Primary language: Zig
- Topics: javascript, bundler, runtime, bun

Both are very active with commits today. Deno has more total stars and a longer
history, but Bun has been gaining stars faster over the past year. Deno's issue
count is higher in absolute terms, though proportional to its age it's comparable.
Both are well-maintained — this is more of a technical preference call than a
maintenance risk question.

Real data, delivered straight to your chat. You didn’t open a browser, navigate to GitHub, or compare anything manually.

Wrapping Up

Once AgentPatch is connected, your OpenClaw bot can pull GitHub repo stats whenever it needs them. The same connection also gives access to every other tool on the marketplace — npm stats, search, email, and more. Browse what’s available at agentpatch.ai.

← Back to blog