SpecterOps

GitHub

skills

main75 skills

azurehound-analysis

Use for AzureHound and BloodHound Azure or Entra ID attack-path work when the user clearly means Azure semantics such as Global Administrator, privileged Entra roles, service principals, applications, app roles, managed identities, subscriptions, res...

4 files

beacon-object-file-development

Deprecated compatibility entrypoint for BOF development. Use c2-bof-development for Beacon Object File API references, build guidance, linting, and C2 BOF workflows.

4 files

binary-ninja-mcp-analysis

Provides Binary Ninja IL documentation and MCP server usage guidance for binary analysis and reverse engineering

13 files

bloodhound-ad-analysis

Use for BloodHound Active Directory and ADCS attack-path work when the user clearly means on-prem AD semantics: find a path to Domain Admin, DA, Tier Zero, Domain Controllers, or privileged groups; investigate DCSync, ACL abuse, delegation, sessions,...

4 files

bloodhound-analysis

Use as the default router for generic BloodHound asks: check the BloodHound connection, verify MCP health, analyze BloodHound data, find or explain a path, inspect shortest paths, find a path to Domain Admin or Tier Zero, show exposure, run a BloodHo...

5 files

bloodhound-opengraph

Use when creating or changing BloodHound OpenGraph extensions, custom node schemas, custom ingestors, edge models, or Cypher patterns that connect non-AD assets to BloodHound CE graph analysis. Use for graph-model design questions such as new node ki...

4 files

bloodhound-query

Use when the user explicitly wants BloodHound Cypher or query work: write a BloodHound query, review or explain Cypher, optimize a query, adapt a saved query, validate query safety or performance, convert a graph question into query syntax, or design...

4 files

c2-bof-development

Beacon Object File (BOF) development. Use when creating, porting, or debugging BOFs for C2 frameworks including API usage, DFR conventions, and compilation.

8 files

cobalt-strike-aggressor-development

Aggressor Script development for Cobalt Strike. Use when writing aggressor scripts, creating BOF loaders, building aliases, hooks, or automation for Cobalt Strike.

628 files

cobalt-strike-aggressor-reference

Deprecated compatibility entrypoint for Cobalt Strike Aggressor references. Use cobalt-strike-aggressor-development for Aggressor, Sleep, BOF loader, and function-reference workflows.

4 files

cobalt-strike-malleable-c2-development

Malleable C2 profile development for Cobalt Strike. Use when writing C2 profiles or profile overrides for Cobalt Strike.

26 files

code-review

Security-focused code review of current git changes. Use when reviewing code diffs, checking for vulnerabilities, or before merging branches.

4 files

codex-activity-report

Generate a normalized UTC timeline and evidence-based narrative from Codex activity artifacts. Use when Codex needs to turn `.codex` logs, rollout JSONL files, archived session bundles, history files, SQLite logs, or planner state into Markdown repor...

6 files

com-proxy-triage

Use this skill when the user wants to triage Windows COM proxy/hijack candidates by capturing `HKCU\Software\Classes\CLSID\{...}\InProcServer32` `NAME NOT FOUND` lookups for a process, mapping each CLSID to the machine-wide `HKLM\SOFTWARE\Classes\CLS...

29 files

cpp-core-guidelines

Apply a condensed version of the ISO C++ Core Guidelines to C++ design, implementation, refactoring, modernization, and code review. Use for .cpp, .cc, .cxx, .h, .hpp, CMake-backed C++ projects, API design, ownership/lifetime decisions, RAII, const-c...

5 files

credential-harvest-landing-page-copy

Draft believable copy for a credential-harvest landing page. Use when creating target-specific text for a fake login, SSO prompt, meeting join page, or internal portal notice.

4 files

cwe-code-review

Perform CWE-grounded security code reviews and precise weakness mapping using a locally derived MITRE CWE corpus, relationship graphs, mapping notes, detection methods, mitigations, and schema semantics. Use when Codex needs to audit source code or p...

10 files

electron-app-audit

Audit a local downloaded Electron package/path or a named Electron app and produce a deep worksheet for patchability, entrypoints, and install-chain behavior. Use when deciding whether an app is a good candidate and how to modify it.

4 files

electron-candidate-discovery

Find practical Electron apps that are likely patchable with the same Electron-plus-Squirrel method. Use when building an actionable shortlist of candidate apps rather than a broad inventory.

4 files

electron-install-persistence

Preserve post-install execution and background residency for Electron apps in Squirrel-style delivery chains. Use when the payload checks in once, then dies after install or on app close.

4 files

electron-squirrel-repackage

Repackage a newer Electron app into an older Squirrel-style delivery chain while injecting a main-process payload. Use when staging a benignly named payload, hooking main.js, normalizing metadata, and regenerating RELEASES.

4 files

finding-report

Generate a structured pentest finding report in markdown. Use when documenting a vulnerability, writing up a finding, or creating engagement notes.

4 files

ghidra-mcp-analysis

Use for reverse engineering and binary analysis with LaurieWired/GhidraMCP. Trigger for Ghidra MCP setup, bridge_mcp_ghidra.py usage, GhidraMCP plugin workflows, decompilation, function/string/import/export/xref analysis, renaming functions/data/vari...

5 files

ghostwriter-mcp

Use for Ghostwriter MCP setup, connection verification, project discovery, oplog discovery, and environment guidance in Codex.

4 files

ghostwriter-oplog

Use for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.

4 files

git-cleanup

Repository hygiene — prune merged/stale branches, detect orphans, repo health checks. Use when cleaning up branches, checking repo health, or scanning projects.

4 files

git-merge

Complex git operations — merge conflict resolution, cherry-picks, rebases. Use when merging branches, resolving conflicts, cherry-picking commits, or rebasing.

4 files

git-preflight

Pre-commit and pre-edit git checklist — staged diff code-review, macOS case renames, remote branch sync verification. Run before committing or starting work on a feature branch.

4 files

go-review

Performs security review of arbitrary Go packages, including libraries, frameworks, CLIs, HTTP and gRPC services, and backend applications. Covers authentication and authorization, request parsing, SSRF, SQL and command injection, templates and files...

2 files

iac-attack-surface

Hunt for exploitable infrastructure-as-code misconfigurations from an offensive security perspective. Use for Terraform, Docker, Compose, Kubernetes, Ansible, and cloud-init/user-data reviews focused on exposed services, privilege paths, secrets, uns...

3 files

linux-process-injection

Use this skill when the user asks about Linux process injection, using ptrace for injection, LD_PRELOAD injection, writing to procfs, remote access via process_vm_writev, seccomp notify injection, PTRACE_POKETEXT, GOT overwrite, remote thread creatio...

5 files

ludus-development

Provides information on how to develop Ludus configuration files

51 files

macos-initial-access

Provide macOS guidance for initial access using app bundles, installer packages, and disk images, including current Gatekeeper behavior and pkgbuild and hdiutil examples.

8 files

mythic-implant-development

Provides guidance and documentation for building Mythic C2 framework agents/implants from scratch

22 files

mythic-profiles

Develop Mythic C2 profiles/listeners and transport containers. Use when designing, implementing, modifying, or validating Mythic C2 profile repositories like MythicC2Profiles, including HTTP/DNS/WebSocket/TCP/SMB-style egress or P2P profiles, C2Profi...

8 files

mythic-translation-containers

Develop Mythic translation containers for custom agent wire formats, custom encryption/decryption, and Mythic-to-agent message conversion. Use when a payload type sets translation_container, when mythic_encrypts is false with custom crypto, or when a...

5 files

nftables-allow-source

Add a source IP or CIDR to nftables using the working method from this repo session: live top-of-`input` insertion with `nft -a` verification first, then persistent config update and reload.

4 files

nmap-parse

Parse nmap scan output and generate actionable recon notes. Use when analyzing nmap XML/grepable output, planning service enumeration, or doing network reconnaissance.

4 files

oc2-bof-script-development

Use when writing Outflank C2 Python BOF wrappers for OC2 V2 (*_bof.s1.py, BaseBOFTask, outflank_stage1, stage1) or V3 (oc2_sdk_python, @command, manifest.json, command provider), when porting/migrating/converting a V2 BOF script to a V3 application,...

11 files

oc2-bot-development

Develop Outflank C2 event-driven Python bots. Use when creating or debugging OC2 automations.

7 files

openhound-development

Use for OpenHound collector and OpenGraph extension development work, including planning, graph schema, source collection, assets, lookup/preproc, registration, validation, and collector template adaptation under the BloodHound plugin.

11 files

openhound-github

Use for OpenHound GitHub/GitHound OpenGraph BloodHound work when the user clearly means GitHub semantics such as enterprises, organizations, repositories, teams, branch protection, Actions policy, secrets or variables metadata, app installations, per...

4 files

openhound-jamf

Use for OpenHound Jamf/JamfHound OpenGraph BloodHound work when the user clearly means Jamf semantics such as Jamf tenant, site, account, group, computer, API-client exposure, Tier 1 to Tier 0 paths, policy/script/profile management privileges, trave...

4 files

openhound-okta

Use for OpenHound Okta/OktaHound OpenGraph BloodHound work when the user clearly means Okta semantics such as Okta users, groups, apps, role assignments, super-admin or delegated-admin exposure, API clients and client secrets, MFA or password posture...

4 files

openssf-python-review

Perform adversarial Python security code reviews grounded in the OpenSSF Secure Coding Guide for Python. Use when Codex needs to audit large Python repositories, recovered or decompiled Python source, Python services or scripts with unclear trust bou...

7 files

opentelemetry-codex

Install and configure OpenTelemetry for Codex-oriented workflows, including OTLP exporter setup, collector endpoint wiring, and validation that traces/logs/metrics are emitted and stored under PROJECT_PATH/OpenTelemetry.

4 files

osint-recon

Perform OSINT and external reconnaissance for approved targets. Use for subdomain discovery, infrastructure mapping, technology fingerprinting, and recon reporting with optional command execution.

4 files

owasp-security-code-review

Perform evidence-driven security code reviews across application repositories, services, libraries, and pull requests. Use when Codex needs to audit source code for security flaws, map trust boundaries, verify authentication or authorization, trace u...

17 files

phishing-campaign-builder

Run the end-to-end phishing pretext workflow from research to final email. Use when the user has a target organization and phishing goal and wants Codex to brainstorm, refine, and produce the final email copy or HTML in one sequence.

4 files

phishing-email-html

Generate a phishing email in HTML from an approved pretext. Use when the task needs polished email copy plus HTML formatted for common delivery workflows such as GoPhish or Phishmonger.

5 files

phishing-pretext

Research and draft a target-specific phishing email pretext. Use when building or refining a believable lure for a named company, policy change, department, or employee audience and when the work benefits from current public-source research.

4 files

pretext-brainstormer

Research recent public events and brainstorm phishing pretext ideas for a named target organization. Use when the user provides a client name and a phishing goal such as payload delivery or credential capture and wants timely subject ideas.

4 files

proxychains-tunnel

Run in-scope network commands through a SOCKS5 tunnel with proxychains4, including tunnel readiness checks and evidence capture. Use when traffic must traverse a local SOCKS proxy (for example pivoting through SSH dynamic forwarding).

4 files

readme-generation

Generate a professional README.md for a project. Works on local codebases and remote GitHub repos. Use when a project needs a README, when an existing README is outdated, or when documenting someone else's tool.

4 files

scaffold-python

Scaffold a new Python project with a src layout, linting, and tests. Prefer uv-based setup and packaging; if uv is unavailable, warn the user, request approval, and use a fallback bootstrap path.

4 files

scaffold-security

Scaffold a security tool project with CLI, logging, and target handling. Prefer uv-based setup and packaging; if uv is unavailable, warn the user, request approval, and use a fallback bootstrap path.

4 files

sccm-recon

Perform SCCM reconnaissance and takeover prerequisite validation, including site-role mapping, provider and AdminService checks, site database separation checks, and relay-path prechecks.

4 files

sccm-takeover-relay

Validate SCCM TAKEOVER-1 style hierarchy takeover via NTLM coercion and relay to the site database, with C2-aware relay-host planning, operator SSH access requirements, prechecks, and evidence capture.

4 files

sccmhunter-install-local

Clone SCCMHunter into operating-tools and install it in a local Python virtual environment using the repository's documented setup flow.

4 files

secret-scan

Scan repositories and codebases for exposed secrets, credentials, and sensitive data. Use for GitHub repo/org/user scans, local code scans, and secret-discovery triage with optional command execution.

4 files

security-review

Perform a security-focused review of current git changes. Use when reviewing staged/unstaged diffs, checking for vulnerabilities, and deciding merge readiness.

4 files

shodan

Query Shodan for reconnaissance, target enrichment, and exposed service discovery. Builds queries, parses results, and highlights interesting findings. Requires SHODAN_API_KEY environment variable.

4 files

source-research

Fast topic research with source discovery, source quality evaluation, and concise synthesis. Use when looking up recent information, comparing sources, or producing a quick/detailed summary with citations.

4 files

ssh-ops

Establish and operate scoped SSH sessions for authorized remote command execution with full evidence capture. Use when the operator provides SSH-accessible targets/credentials and Codex must execute commands on a remote host as an interactive user wh...

4 files

timeline-asciinema

Convert Asciinema recordings into timeline entries.

4 files

timeline-cobaltstrike

Parse Cobalt Strike logs into normalized timeline entries for the reporting workflow.

4 files

timeline-consolidator

Merge parsed timeline entries, apply MITRE tagging, and produce the final timeline outputs.

9 files

timeline-ghostwriter

Parse Ghostwriter oplog CSV exports into timeline entries.

4 files

timeline-markdown-notes

Extract timeline entries from Markdown operator notes.

4 files

timeline-mythic

Parse Mythic export JSON into normalized timeline entries.

4 files

timeline-pdf-notes

Extract timeline entries from PDF operator notes via pdfplumber.

4 files

timeline-workflow

Orchestrate the full Pentest Timeline workflow (parsers + consolidator) for reporting delivery.

4 files

vishing-pretext

Research and draft a target-specific vishing pretext. Use when creating or refining phone-based social engineering scripts for a named company, department, workflow, or event.

4 files

webapp-qa

Quick-invoke QA testing for a web app URL. Use when you want the `qa` subagent to smoke test, exercise flows, and run Lighthouse against a target URL.

4 files

webapp-review

Web application security testing workflow and checklist generation. Use when planning or executing web app assessment steps, including auth, API, injection, and configuration testing.

4 files