security-scan-tf

Scan active Techfolk-AS repositories for malicious code patterns and report severity ratings.

Updated Mar 24, 2023
One-click install
npx skills add https://github.com/j4hr3n/dotfiles --skill security-scan-tf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scan-tf
Source: https://github.com/j4hr3n/dotfiles/tree/main/configs/claude-code/skills/security-scan-tf
Command: npx skills add https://github.com/j4hr3n/dotfiles --skill security-scan-tf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deep security scan of all active repos in the Techfolk-AS GitHub organization, looking for malicious code patterns, hardcoded secrets, obfuscated code, backdoors, and suspicious behavior. Use this skill when you want to scan Techfolk repos, check org security, or perform a security audit. It responds to questions like "is our code safe" or "any suspicious code in our repos" for the Techfolk-AS organization.

Core Features & Use Cases

  • Deep multi-repo security scanning across all active Techfolk-AS repositories to identify code-level threats.
  • Parallelized per-repo analysis with aggregated findings and severity ratings.
  • Consolidated report generation with per-repo details and recommended mitigations for security audits and ongoing hygiene.

Quick Start

Ask me to run a security scan on all active Techfolk-AS repositories to detect backdoors, secrets, and suspicious code patterns.

Frequently Asked Questions about security-scan-tf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security audit on all active GitHub repositories in an organization?

To run a security audit on active GitHub repositories, you can use this skill to enumerate non-archived repos via GitHub CLI, shallow-clone each one, and generate a consolidated report with severity ratings for malicious patterns and secrets.

How can I scan my codebase for backdoors and hardcoded secrets?

Scanning your codebase for backdoors and hardcoded secrets is done by shallow-cloning repositories and analyzing the code for malicious patterns, obfuscated code, and suspicious behavior to produce a per-repo security report.

Does this security scan require the GitHub CLI to enumerate organization repositories?

Yes, this security scan requires the GitHub CLI to enumerate non-archived repositories within the Techfolk-AS organization before shallow-cloning and analyzing them for code-level threats.

What types of malicious code patterns can be detected during a repository security scan?

A repository security scan detects code-level malicious patterns including hardcoded secrets, obfuscated code, backdoors, and suspicious behavior across all active repositories.

Can I generate a consolidated security report with severity ratings for multiple repositories?

Yes, you can generate a consolidated security report with per-repo details, aggregated findings, severity ratings, and recommended mitigations after completing parallelized analysis across your active repositories.

What is the best way to perform an organization-wide security review for suspicious code?

An organization-wide security review for suspicious code is best performed by parallelizing per-repo analysis across all active repositories, identifying code-level threats, and aggregating the findings into a consolidated report with recommended mitigations.