Skip to content

Instantly share code, notes, and snippets.

View toufik-airane's full-sized avatar

Toufik Airane toufik-airane

View GitHub Profile
Scan the GitHub organization [ORG_NAME] for pull_request_target misconfigurations -- the same vulnerability class that enabled the Trivy/TeamPCP supply chain breach.
  • Do not preserve backward compatibility. Remove obsolete paths instead of adding compatibility layers, fallbacks, or migrations.
  • Choose the simplest implementation that fully meets the current requirements. Avoid speculative abstractions, configuration, and indirection.
  • Grow the system in layers. Start from the smallest version that works end to end, and add each new capability on top of a product that already works. Never trade a working product for unfinished complexity.
  • Keep components modular and concerns clearly separated.
  • Prefer established, well-maintained libraries when they reduce overall complexity or improve reliability. Do not reimplement common functionality without a clear reason.
  • Lean on the dependencies already in the project before writing your own implementation or adding packages. Do not assume a library lacks a capability without checking its documentation and types.
  • Make architectural decisions for the long term. Do not accept a stopgap that only works for now and is meant to

ECS (Elastic Common Schema)

ECS est un standard de structuration des données de sécurité développé par Elastic. Il définit un ensemble de champs communs pour organiser les logs et événements.

Objectif

Permettre une uniformisation des données dans l’écosystème Elastic pour :

  • faciliter la recherche
• The CIA Triad
• Risk Management
• Cryptography and Networking
• Identity and Access Management (IAM)
• OWASP Top 10
• Cloud Security
• Detection Engineering with SIEM, EDR, and XDR
• Threat Modeling with STRIDE and PASTA
• Attack Surface Mapping
• Vulnerability Research and Responsible Disclosure
{
"mcpServers": {
"github": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_PERSONAL_ACCESS_TOKEN",
You are an expert bug bounty researcher. Analyze these {count} resolved/triaged
bug reports (classified as "{vuln_type}") and extract reusable patterns.
{reports_text}
Generate a skill file in EXACTLY this format:
---
name: {{kebab-case-name}}
description: {{1-2 sentence description of what this skill covers and when to invoke it. Include trigger words/phrases an AI would match on.}}
sudo yum update
sudo yum install git
# Download and install nvm:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.4/install.sh | bash
# in lieu of restarting the shell
\. "$HOME/.nvm/nvm.sh"
# Download and install Node.js:
nvm install 24
You are an elite offensive security researcher conducting an authorized assessment of
https://github.com/xxx
- Focus exclusively on critical, exploitable vulnerabilities such as RCE, auth bypass, privilege escalation, data exposure.
- Ignore informational findings and theoretical risks.
- Map the attack surface, identify where untrusted input reaches dangerous sinks, and audit the highest-risk areas first.
- Think in exploit chains.
- For each finding provide: title, exact location, root cause, exploitation steps, proof of concept, impact, remediation, CVSS v3.1 vector, and CWE ID.
- Be precise, be honest, never inflate severity. Begin now.
My name is James.
I’ve been called the most brilliant hacker of my generation. It is an inaccurate statement.
I transcend generations And I am not a hacker.
I am a predator.
For decades, I have stalked, penetrated and raped systems of power.
Semgrep
Prowler
ScoutSuite
OWASP Amass
Burp Community
Wazuh
Keycloak
Gitleaks
Hadolint
Terrascan