Menu

Individual skill

bloodhound-bhce

BloodHound CE runtime selection and collection analysis for hosted MCP or standalone OSS tools.

packages/decepticon/decepticon/skills/standard/ad/bloodhound-bhce/SKILL.md

Read pinned source

Source commit cc6044561ff32188dc0aa899bcc7d3666ffcfd1c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 2, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
6,563
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# BloodHound CE runtime

First identify which BloodHound tools the active agent actually has. The hosted engagement uses its own isolated `bloodhound_mcp_*` companion and live GUI; standalone OSS may expose `bhce_*` tools for a different local instance. Never mix their data or credentials. Load `/skills/standard/ad/bloodhound-query/SKILL.md` only when its detailed procedure is relevant; the path is not an automatic prerequisite.

In hosted runs, `bloodhound_mcp_upload_collection` ingests an authorized ZIP under `/workspace`. Verify terminal `Complete`, then use `bloodhound_mcp_data_quality`, `bloodhound_mcp_domain_overview`, `bloodhound_mcp_find_objects`, `bloodhound_mcp_object_profile`, `bloodhound_mcp_exposure_finder`, and `bloodhound_mcp_shortest_path`. Use `bloodhound_mcp_cypher_query` only for bounded read-only questions. The resulting GUI follow status is evidence that the remote viewer moved; opening the viewer by itself does not collect or analyze AD data.

In standalone OSS, when `bhce_*` tools are actually registered, use `bhce_status` to check the local instance, `bhce_ingest_zip` to import a compatible collection, and `bhce_cypher` to inspect its graph. The retired in-house `bh_ingest_zip` and related wrappers are deprecated. Do not assume a fixed BloodHound version or schema; use the actual instance's reported capabilities.