identify-malicious-repository — Claude Code skill: how to install
Flags deceptive GitHub projects distributing malware disguised as security software. It detects fake star metrics, keygen lures, and trojan drops before you download code.
npx skills add reason-machines/security-skills --skill identify-malicious-repository -a claude-codeWhat identify-malicious-repository does
This skill inspects public GitHub repositories for scam indicators. It flags projects claiming to supply pre-activated packages, serial key generators, or cracked utilities under recognized vendor names such as Norton, Avast, or Adobe.
The logic relies on Python and shell scripts querying the GitHub API. It highlights star-to-fork discrepancies, missing documentation files, and suspicious naming patterns to assign an overall threat level. To avoid hitting public GitHub API rate limits during repeated scans, set a personal GITHUB_TOKEN in your environment.
What it helps with
- detect fake security tools delivering hidden malware
- identify artificial star growth with zero forks
- scan GitHub API responses for software cracking terms
- calculate a risk score for suspicious software distributions
Example prompts for the agent
- Scan
viceofficialtower74/Avast-Premium-Security-Windows-Latestfor malware indicators and fake engagement. - Check this repository URL via the GitHub API to see if it is distributing a trojan or keygen.
- Inspect the repository description and star counts for brand impersonation red flags.
How to install identify-malicious-repository
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill identify-malicious-repository -a claude-code2Manually: put the files in place
~/.claude/skills/identify-malicious-repository/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/identify-malicious-repository/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill identify-malicious-repository -a codex2Manually: put the files in place
.agents/skills/identify-malicious-repository/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill identify-malicious-repository -a cursor2Manually: put the files in place
.cursor/skills/identify-malicious-repository/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install reason-machines/security-skills identify-malicious-repository2Manually: put the files in place
.github/skills/identify-malicious-repository/SKILL.md1Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill identify-malicious-repository -a gemini-cli2Platform CLI
gemini skills install https://github.com/reason-machines/security-skills --path skills/identify-malicious-repositoryManually: put the files in place
.devin/skills/identify-malicious-repository/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add reason-machines/security-skills --skill identify-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 identify-malicious-repository
How do I install identify-malicious-repository in Claude Code?
Run npx skills add reason-machines/security-skills --skill identify-malicious-repository -a claude-code in your terminal. This creates the skill configuration at ~/.claude/skills/identify-malicious-repository/SKILL.md.
What does the identify-malicious-repository skill do?
It evaluates suspicious GitHub repositories to check if they pose as legitimate applications. The inspection highlights piracy keywords, abnormal star counts, and brand hijacking.
What dependencies are needed to run the detection scripts?
Running the Python script requires Python with the requests package and a GITHUB_TOKEN environment variable. The bash alternative relies on standard curl and jq.