report-malicious-repository — Claude Code skill: spot fake repos
Flags repositories that pose as antivirus or other commercial software and walks you through filing a GitHub report.
npx skills add reason-machines/security-skills --skill report-malicious-repository -a claude-codeWhat report-malicious-repository does
The skill reads repository metadata against a list of red flags: piracy words like keygen, crack, loader or serial in the description, antivirus brand names used without authorization, a missing README, no source code, a fresh account with inflated stars. It counts the hits and assigns a risk level from LOW to CRITICAL.
Inside are Go functions that analyze the description and topics, check for brand impersonation and weigh repository age, plus a script that calls the GitHub API and prints every flag it finds. That script needs GITHUB_TOKEN in your environment; without it the call fails. GitHub has no public API for abuse reports, so the script only prints the report URL and the text to paste — you submit it through the web form.
A ready report template covers the repository name, the violation type, a description and the evidence. The checks are heuristics, so a legitimate project with the word premium in its description will also trip them. Open the repo and read the code before you report anything.
What it helps with
- tell a fake antivirus repo from a real project
- check a repo with keygen in its description for malware signs
- gather evidence for a GitHub abuse report
- score repository metadata by risk level
- filter suspicious dependencies during a scan
Example prompts for the agent
- check DragonflyTomb/Avast-Premium-Security-2026 for malware red flags
- draft a GitHub report for this repository
- what red flags does this project with keygen in the description have?
How to install report-malicious-repository
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill report-malicious-repository -a claude-code2Manually: put the files in place
~/.claude/skills/report-malicious-repository/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/report-malicious-repository/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill report-malicious-repository -a codex2Manually: put the files in place
.agents/skills/report-malicious-repository/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill report-malicious-repository -a cursor2Manually: put the files in place
.cursor/skills/report-malicious-repository/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/security-skills report-malicious-repository2Manually: put the files in place
.github/skills/report-malicious-repository/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill report-malicious-repository -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/security-skills --path skills/report-malicious-repositoryManually: put the files in place
.devin/skills/report-malicious-repository/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill report-malicious-repository -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about report-malicious-repository
How do I install report-malicious-repository in Claude?
Run npx skills add reason-machines/security-skills --skill report-malicious-repository -a claude-code. The skill lands at ~/.claude/skills/report-malicious-repository/SKILL.md.
What does report-malicious-repository do?
It looks for signs of a malicious repository — piracy keywords, brand impersonation, missing source code — and assigns a risk level. Then it helps you file a report through GitHub's form.
What does the skill need to run?
Scanning through the GitHub API requires a GITHUB_TOKEN environment variable. The report itself still goes through the web form, since GitHub has no public API for abuse reports.