specterops
- 89 skills
- 0 followers
- 740 repo stars
- 6 days ago last updated
- ▌ Openhound Development · specterops bundleUse 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.
- ▌ Oc2 Ops · specterops bundleOperate Outflank C2 for authorized red team operations using its MCP. Use when the user asks to list implants, run implant commands, or otherwise interact with OC2.
- ▌ Cobalt Strike Ops · specterops bundleOperate Cobalt Strike for authorized red team operations using its MCP. Use when the user asks to list Beacons, run Beacon commands, or otherwise interact with Cobalt Strike.
- ▌ Cwe Code Review · specterops bundlePerform 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 pull requests, identify root-cause weakness classes, distinguish broad symptoms from mappable CWEs, justify CWE IDs in findings, or review code against CWE views such as Software Development, Research Concepts, Top 25, OWASP, language-specific, or AI/ML weakness sets.
- ▌ Openssf Python Review · specterops bundlePerform 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 boundaries, or code paths involving Python-specific injection, deserialization, archive extraction, import-path, encoding, numeric, concurrency, logging, exception, resource-management, secret-handling, or randomness risks.
- ▌ Owasp Security Code Review · specterops bundlePerform 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 untrusted data to sensitive sinks, assess business logic or cryptography, or produce prioritized findings when no narrower language or platform review skill fits.
- ▌ Go Review · specterops bundlePerforms 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 filesystems, crypto/session handling, concurrency, and unsafe/cgo edges.
- ▌ Sccm Recon · specterops bundlePerform SCCM reconnaissance and takeover prerequisite validation, including site-role mapping, provider and AdminService checks, site database separation checks, and relay-path prechecks.
- ▌ Secret Scan · specterops bundleScan 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.
- ▌ Ludus Development · specterops bundleProvides information on how to develop Ludus configuration files
- ▌ Webapp Review · specterops bundleWeb application security testing workflow and checklist generation. Use when planning or executing web app assessment steps, including auth, API, injection, and configuration testing.
- ▌ Openhound Jamf · specterops bundleUse 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, traversable Jamf edges, Jamf SSO links, Okta/Jamf hybrid links, or Jamf device-management attack-path analysis. Do not use for generic BloodHound path triage, connection checks, explicit Cypher authoring/review, or non-Jamf OpenGraph domains.
- ▌ Openhound Okta · specterops bundleUse 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, AD agents, identity providers, inbound or outbound hybrid paths, SCIM provisioning, or GitHub/Azure/Jamf/Entra linked identity paths. Do not use for generic BloodHound path triage, connection checks, explicit Cypher authoring/review, or non-Okta OpenGraph domains.
- ▌ Mythic Profiles · specterops bundleDevelop 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, C2Profile parameters, server binaries, redirector material, OPSEC checks, and payload-type integration.
- ▌ Shodan · specterops bundleQuery Shodan for reconnaissance, target enrichment, and exposed service discovery. Builds queries, parses results, and highlights interesting findings. Requires SHODAN_API_KEY environment variable.
- ▌ Security Review · specterops bundlePerform a security-focused review of current git changes. Use when reviewing staged/unstaged diffs, checking for vulnerabilities, and deciding merge readiness.
- ▌ Ssh Ops · specterops bundleEstablish 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 while enforcing OPSEC gating and safe-check behavior.
- ▌ Bloodhound Query · specterops bundleUse 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 follow-up graph questions across BloodHound CE/BHE, AzureHound, OpenHound GitHub, OpenHound Jamf, OpenHound Okta, or other OpenGraph data. Do not use as the default entry skill for generic path triage, connection checks, or AD/Azure/OpenHound exposure analysis when no explicit query-authoring task is requested.
- ▌ Openhound Github · specterops bundleUse 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, personal access tokens, GitHub-to-Azure OIDC or federated identity paths, SAML external identities, or SSO/SCIM links from Azure, Okta, or SCIM identities. Do not use for generic BloodHound path triage, connection checks, explicit Cypher authoring/review, or non-GitHub OpenGraph domains.
- ▌ Electron App Audit · specterops bundleAudit 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.
- ▌ Webapp QA · specterops bundleQuick-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.
- ▌ Sccm Takeover Relay · specterops bundleValidate 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.
- ▌ Nmap Parse · specterops bundleParse nmap scan output and generate actionable recon notes. Use when analyzing nmap XML/grepable output, planning service enumeration, or doing network reconnaissance.
- ▌ Azurehound Analysis · specterops bundleUse 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, resource groups, VMs, Key Vaults, or hybrid AD/Azure paths. Do not use for generic BloodHound connection checks, unclear graph-domain triage, explicit Cypher authoring/review, or OpenGraph schema-extension work.
- ▌ Bloodhound Analysis · specterops bundleUse 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 BloodHound query, or triage graph results when the domain is not yet clear. Use BloodHound MCP for authorized BloodHound CE graph analysis, path triage, object lookup, data-quality checks, AD/ADCS/Azure/OpenGraph exposure mapping, and report-ready remediation output. Do not use for unrelated network recon or for domain-specific work that is clearly AzureHound, OpenHound, OpenGraph schema design, or explicit Cypher authoring/review.
- ▌ Code Review · specterops bundleSecurity-focused code review of current git changes. Use when reviewing code diffs, checking for vulnerabilities, or before merging branches.
- ▌ Osint Recon · specterops bundlePerform OSINT and external reconnaissance for approved targets. Use for subdomain discovery, infrastructure mapping, technology fingerprinting, and recon reporting with optional command execution.
- ▌ Finding Report · specterops bundleGenerate a structured pentest finding report in markdown. Use when documenting a vulnerability, writing up a finding, or creating engagement notes.
- ▌ Bloodhound Opengraph · specterops bundleUse 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 kinds, new relationship kinds, extension schema changes, or custom ingestor behavior. Do not use for routine BloodHound path triage, connection checks, or known OpenHound query adaptation; use $bloodhound-analysis, $bloodhound-query, $openhound-github, $openhound-jamf, or $openhound-okta instead.
- ▌ Ghostwriter MCP · specterops bundleUse for Ghostwriter MCP setup, connection verification, project discovery, oplog discovery, and environment guidance in Codex.
- ▌
- ▌ Git Merge · specterops bundleComplex git operations — merge conflict resolution, cherry-picks, rebases. Use when merging branches, resolving conflicts, cherry-picking commits, or rebasing.
- ▌ C2 Bof Development · specterops bundleBeacon Object File (BOF) development. Use when creating, porting, or debugging BOFs for C2 frameworks including API usage, DFR conventions, and compilation.
- ▌ Bloodhound Ad Analysis · specterops bundleUse 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, local admin, trusts, GPO abuse, LAPS/gMSA, Kerberoasting, AS-REP roasting, or ADCS ESC paths; or explain AD hygiene and privilege exposure in a BloodHound graph. Do not use for generic BloodHound connection checks, unclear graph-domain triage, explicit Cypher authoring/review, or Azure/OpenHound/OpenGraph-specific work.
- ▌ Oc2 Bot Development · specterops bundleDevelop Outflank C2 event-driven Python bots. Use when creating or debugging OC2 automations.
- ▌ Sccmhunter Install Local · specterops bundleClone SCCMHunter into operating-tools and install it in a local Python virtual environment using the repository's documented setup flow.
- ▌ Ghostwriter Oplog · specterops bundleUse for Ghostwriter operation log entries from Codex, including config guidance, quick notes, evidence-backed entries, and guided oplog capture through the Ghostwriter MCP tools.
- ▌ Timeline Workflow · specterops bundleOrchestrate the full Pentest Timeline workflow (parsers + consolidator) for reporting delivery.
- ▌ Git Cleanup · specterops bundleRepository hygiene — prune merged/stale branches, detect orphans, repo health checks. Use when cleaning up branches, checking repo health, or scanning projects.
- ▌
- ▌ Timeline PDF Notes · specterops bundleExtract timeline entries from PDF operator notes via pdfplumber.
- ▌ Vishing Pretext · specterops bundleResearch 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.
- ▌ Source Research · specterops bundleFast 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.
- ▌ Phishing Pretext · specterops bundleResearch 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.
- ▌ Macos Initial Access · specterops bundleProvide macOS guidance for initial access using app bundles, installer packages, and disk images, including current Gatekeeper behavior and pkgbuild and hdiutil examples.
- ▌ Com Proxy Triage · specterops bundleUse 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\CLSID\{...}\InProcServer32` DLL, and optionally testing HKCU overrides with a Koppeling-style proxy DLL. Good for Zoom, Edge, and similar COM activation hunts.
- ▌ Git Preflight · specterops bundlePre-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.
- ▌ Mythic Implant Development · specterops bundleProvides guidance and documentation for building Mythic C2 framework agents/implants from scratch
- ▌ Electron Squirrel Repackage · specterops bundleRepackage 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.
- ▌
- ▌ Iac Attack Surface · specterops bundleHunt 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, unsafe defaults, workload escape, lateral movement, persistence, and assessment-ready findings.
- ▌ Proxychains Tunnel · specterops bundleRun 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).
- ▌ Electron Candidate Discovery · specterops bundleFind 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.
- ▌ Electron Install Persistence · specterops bundlePreserve 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.
- ▌ Timeline Cobaltstrike · specterops bundleParse Cobalt Strike logs into normalized timeline entries for the reporting workflow.
- ▌ Timeline Consolidator · specterops bundleMerge parsed timeline entries, apply MITRE tagging, and produce the final timeline outputs.
- ▌ Scaffold Python · specterops bundleScaffold 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.
- ▌ Cpp Core Guidelines · specterops bundleApply 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-correctness, templates, concurrency, error handling, performance, C interop, and standard-library usage.
- ▌ Phishing Email HTML · specterops bundleGenerate 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.
- ▌ Mythic Translation Containers · specterops bundleDevelop 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 C2 profile/agent needs non-JSON or binary message formats.
- ▌ Opentelemetry Codex · specterops bundleInstall 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.
- ▌
- ▌ Ghidra MCP Analysis · specterops bundleUse 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/variables, setting comments/types/prototypes, or producing Ghidra-backed RE notes.
- ▌ Pretext Brainstormer · specterops bundleResearch 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.
- ▌ Readme Generation · specterops bundleGenerate 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.
- ▌ Scaffold Security · specterops bundleScaffold 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.
- ▌ Oc2 Bof Script Development · specterops bundleUse 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, or when passing an existing @artifacts/ catalog file.
- ▌ Nftables Allow Source · specterops bundleAdd 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.
- ▌ Linux Process Injection · specterops bundleUse 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 creation on Linux, or bypassing Yama ptrace restrictions.
- ▌ Codex Activity Report · specterops bundleGenerate 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 reporting under `reports/`, especially for after-action reporting, operator handoff, chronology reconstruction, or evidence-backed engagement summaries.
- ▌ Beacon Object File Development · specterops bundleDeprecated compatibility entrypoint for BOF development. Use c2-bof-development for Beacon Object File API references, build guidance, linting, and C2 BOF workflows.
- ▌ Phishing Campaign Builder · specterops bundleRun 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.
- ▌ Binary Ninja MCP Analysis · specterops bundleProvides Binary Ninja IL documentation and MCP server usage guidance for binary analysis and reverse engineering
- ▌ Cobalt Strike Aggressor Reference · specterops bundleDeprecated compatibility entrypoint for Cobalt Strike Aggressor references. Use cobalt-strike-aggressor-development for Aggressor, Sleep, BOF loader, and function-reference workflows.
- ▌ Cobalt Strike Aggressor Development · specterops bundleAggressor Script development for Cobalt Strike. Use when writing aggressor scripts, creating BOF loaders, building aliases, hooks, or automation for Cobalt Strike.
- ▌ Cobalt Strike Malleable C2 Development · specterops bundleMalleable C2 profile development for Cobalt Strike. Use when writing C2 profiles or profile overrides for Cobalt Strike.
- ▌ Credential Harvest Landing Page Copy · specterops bundleDraft 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.
- ▌ Session Analysis · specterops bundleSafely interpret and communicate findings from AI coding-agent session data. Use when analyzing paired exported session-report JSON and text files (including Blacklight Codex reports), approved `.codex` session artifacts, session-history JSON/JSONL, tool activity, or aggregate session metrics; when comparing sessions, identifying authorized security-assessment attack-path pivots, or explaining privacy and data-handling implications.
- ▌ Blacklight Add Agent Artifact · specterops bundleAdd a newly supported AI agent/tool or a newly discovered artifact file, directory, or glob to Blacklight while keeping Scout and Rules catalogs, generated target tables, schemas, and validation surfaces aligned. Use for requests to add agent support, register an artifact path, extend an existing agent directory inventory, or scaffold cross-platform target metadata.
- ▌ Grill Me · specteropsInterview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- ▌ Openhound · specterops bundleUse for all OpenHound collector work, including planning, graph schema, source collection, assets, lookup/preproc, registration, and validation.
- ▌ Openhound Edge Docs · specterops bundleUse when creating, reviewing, or improving OpenHound/BloodHound OpenGraph edge description markdown for Okta, GitHub, Jamf, or other OpenGraph extensions with Abuse Info, an optional Reverting Abuse Actions subsection, Opsec Considerations, platform-specific references, UI/API steps, and validation checks.
- ▌ Openhound Entity Panels · specterops bundleAdd, migrate, review, or validate BloodHound OpenGraph entity-panel definitions for OpenHound node and relationship kinds on template-capable targets. Covers consolidated descriptions, mandatory direct-traversable relationship summaries, node-specific dynamic Cypher Explore links derived from graph evidence and saved searches, and upload-safe Markdown. Do not use for documentation-only edits that do not change entity panels.
- ▌ Janus Analyzer Skill · specterops bundleUse this skill for Janus requests that ask what to measure, how to measure it, which analyzer should answer it, or how to implement or adjust source-aware analysis for Mythic or Ghostwriter telemetry.
- ▌ Janus Ingestor Creation · specterops bundleUse this skill for Janus requests to design, add, or adjust source ingestors/parsers for live APIs or local files, including Mythic, Ghostwriter, Cobalt Strike REST, Outflank implant logs, new C2 telemetry sources, parser normalization, pull/load CLI wiring, source metadata, retention policy handling, and Docker janus-cli integration.
- ▌ Janus Insight Interpreter · specterops bundleUse this skill for Janus requests that ask for insights from any Janus artifact, including report HTML, bundles, analyzer outputs, events.ndjson, raw exports, or standalone JSON snippets.
- ▌ Managing Packages · specteropsManages Python package dependencies. Use when adding, upgrading, removing, or syncing Python/pypi packages in projects or libs.
- ▌ Addressing Dependabot · specteropsAddresses GitHub Dependabot security alerts by listing open alerts, identifying affected Python/uv, frontend npm, and Titus Go projects, upgrading vulnerable dependencies, running verification, and committing fixes. Use when the user wants to fix Dependabot alerts, upgrade vulnerable packages, or address security vulnerabilities found by Dependabot.
- ▌ Enrichment Module Builder · specteropsBuild a new Nemesis file enrichment module end-to-end with explicit user approval gates for output mode, library choice, sample files, and integration testing.