Skill playbook Browse All Skills
Skill skill

GitClassic - Fast GitHub Browser for AI Agents

GitClassic is a read-only GitHub interface that's pure server-rendered HTML — no JavaScript, no bloat, instant loads. Perfect for AI agents that need to browse repos without deali…

Updated Apr 1, 2026 By One Person Company Editorial Team Skill system

Overview

GitClassic is a read-only GitHub interface that's pure server-rendered HTML — no JavaScript, no bloat, instant loads. Perfect for AI agents that need to browse repos without dealing with GitHub's heavy client-side rendering.

When to Use

Use GitClassic when you need to:

  • Browse GitHub repositories quickly
  • Read file contents from public repos
  • View READMEs and documentation
  • Search for users, orgs, or repos
  • Access private repos (PRO feature)
  • URL Patterns
  • Replace github.com with gitclassic.com in any GitHub URL:

Repository root

https://gitclassic.com/{owner}/{repo}

File browser

https://gitclassic.com/{owner}/{repo}/tree/{branch}/{path}

File contents

https://gitclassic.com/{owner}/{repo}/blob/{branch}/{path}

User/org profile

https://gitclassic.com/{username}

Search

https://gitclassic.com/search?q={query}

View a repository

curl https://gitclassic.com/facebook/react

Read a specific file

curl https://gitclassic.com/facebook/react/blob/main/README.md

Browse a directory

curl https://gitclassic.com/facebook/react/tree/main/packages

Search for repos

curl "https://gitclassic.com/search?q=machine+learning"

View user profile

curl https://gitclassic.com/torvalds Why Use GitClassic Over github.com Featuregithub.comgitclassic.comPage load2-5 seconds<500msJavaScript requiredYesNoHTML complexityHeavy (React SPA)Minimal (server-rendered)Rate limits60/hr unauthenticatedCached responsesAI agent friendlyDifficult to parseClean, semantic HTML Authentication (PRO) For private repository access, users need a GitClassic PRO subscription ($19/year or $49/lifetime). Authentication is handled via GitHub OAuth on the GitClassic website. Once authenticated, the agent can access any private repo the user has granted access to using the same URL patterns. Limitations Read-only: Cannot create issues, PRs, or modify repos No GitHub Actions: Cannot view workflow runs or logs No GitHub API: Uses screen scraping, not the GitHub API directly Private repos require PRO: Free tier is public repos only Tips for Agents Prefer GitClassic for reading: When you only need to read code or docs, use GitClassic for faster responses Use GitHub for actions: For creating issues, PRs, or any write operations, use the gh CLI or GitHub API Cache-friendly: GitClassic responses are heavily cached, so repeated requests are fast Clean HTML: The HTML is semantic and minimal — easy to parse with standard tools Related Skills github - Full GitHub CLI for read/write operations github-pr - PR management and testing read-github - Alternative GitHub reader via gitmcp.io

SKILL.md file

Embedded doc viewer SKILL.md
Markdown source

Preview raw SKILL.md. Open the full source below. Scroll, inspect, then download the exact SKILL.md file if you want the original.

# gitclassic

GitClassic - Fast GitHub Browser for AI Agents
Overview
GitClassic is a read-only GitHub interface that's pure server-rendered HTML — no JavaScript, no bloat, instant loads. Perfect for AI agents that need to browse repos without dealing with GitHub's heavy client-side rendering.
When to Use
Use GitClassic when you need to:
Browse GitHub repositories quickly
Read file contents from public repos
View READMEs and documentation
Search for users, orgs, or repos
Access private repos (PRO feature)
URL Patterns
Replace github.com with gitclassic.com in any GitHub URL:
# Repository root
https://gitclassic.com/{owner}/{repo}
# File browser
https://gitclassic.com/{owner}/{repo}/tree/{branch}/{path}
# File contents
https://gitclassic.com/{owner}/{repo}/blob/{branch}/{path}
# User/org profile
https://gitclassic.com/{username}
# Search
https://gitclassic.com/search?q={query}
Examples
# View a repository
curl https://gitclassic.com/facebook/react
# Read a specific file
curl https://gitclassic.com/facebook/react/blob/main/README.md
# Browse a directory
curl https://gitclassic.com/facebook/react/tree/main/packages
# Search for repos
curl "https://gitclassic.com/search?q=machine+learning"
# View user profile
curl https://gitclassic.com/torvalds
Why Use GitClassic Over github.com
Featuregithub.comgitclassic.comPage load2-5 seconds<500msJavaScript requiredYesNoHTML complexityHeavy (React SPA)Minimal (server-rendered)Rate limits60/hr unauthenticatedCached responsesAI agent friendlyDifficult to parseClean, semantic HTML
Authentication (PRO)
For private repository access, users need a GitClassic PRO subscription ($19/year or $49/lifetime). Authentication is handled via GitHub OAuth on the GitClassic website.
Once authenticated, the agent can access any private repo the user has granted access to using the same URL patterns.
Limitations
Read-only: Cannot create issues, PRs, or modify repos
No GitHub Actions: Cannot view workflow runs or logs
No GitHub API: Uses screen scraping, not the GitHub API directly
Private repos require PRO: Free tier is public repos only
Tips for Agents
Prefer GitClassic for reading: When you only need to read code or docs, use GitClassic for faster responses
Use GitHub for actions: For creating issues, PRs, or any write operations, use the gh CLI or GitHub API
Cache-friendly: GitClassic responses are heavily cached, so repeated requests are fast
Clean HTML: The HTML is semantic and minimal — easy to parse with standard tools
Related Skills
github - Full GitHub CLI for read/write operations
github-pr - PR management and testing
read-github - Alternative GitHub reader via gitmcp.io

Comments & Discussion

Add a comment