Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
GitClassic
v1.0.0Fast, no-JavaScript GitHub browser optimized for AI agents. Browse public repos, read files, view READMEs with sub-500ms load times. PRO adds private repo access via GitHub OAuth.
⭐ 0· 2.8k·6 current·6 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (fast, no-JS GitHub reader) matches the SKILL.md examples and URL patterns. The documented capabilities (read-only browsing of public repos, README viewing, search) are exactly the actions the SKILL.md instructs the agent to perform via HTTP GETs to gitclassic.com.
Instruction Scope
SKILL.md only instructs the agent to fetch pages from gitclassic.com (curl examples and URL patterns). It does not instruct reading local files, environment variables, or transmitting data to unrelated endpoints. The doc explicitly states read-only and screen-scraping behavior.
Install Mechanism
There is no install step or bundled code — this is an instruction-only skill. Nothing gets written to disk and no third-party packages are pulled by the skill itself.
Credentials
The skill declares no required env vars or credentials, which is proportional for public repo browsing. The doc mentions a PRO private-repo feature via GitHub OAuth but provides no concrete agent instructions for using OAuth tokens or cookies; this is an implementation/detail gap (not necessarily malicious) that could affect how private access is handled.
Persistence & Privilege
always is false and the skill is user-invocable only; it requests no persistent privileges or system configuration changes. Autonomous invocation is allowed (platform default) but that alone is expected and not flagged.
Assessment
This skill is internally consistent and low-risk in that it only tells the agent to fetch HTML from gitclassic.com and has no install or secret requirements. Before using it, consider: (1) trust: requests go to a third-party mirror — verify you trust gitclassic.com and its privacy policy; (2) private repos: the PRO feature requires granting GitClassic OAuth access to your GitHub account — only do this if you trust the service because it can view your private repo contents; (3) data leakage: when the agent fetches files or repo pages, their contents transit the third-party domain and may be cached or logged by that service; avoid using the skill for sensitive code unless you accept that risk; (4) missing details: the SKILL.md doesn't explain how an agent should present OAuth tokens/cookies, so private-repo workflows may require extra configuration; (5) for write actions or sensitive operations, prefer the official GitHub API/CLI. If you decide to proceed, review the provider's TLS/certificate, privacy policy, and OAuth scopes before granting access.Like a lobster shell, security has layers — review code before you run it.
latestvk97a5326sfjy82addfwbmtzhdh808ztf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.