OpenHound GitHub / GitHound

Use this skill for OpenHound GitHub OpenGraph query design and attack-path triage with GitHound-collected GitHub data.

Required context

• Authorized GitHub enterprises, organizations, and repositories.
• Whether GitHound/OpenHound GitHub schema/data is loaded.
• Whether SAML external identity, SCIM, Azure, Okta, or other linked identity data is available.
• Target repositories, teams, users, actions policies, environments, secrets, PATs, apps, or cloud identities.

Workflow

1. Read ../../references/docs/bloodhound-query-methodology.md, ../../references/docs/openhound-github-methodology.md, and ../../references/docs/collector-source-index.md.
2. If SCIM, SAML, SSO, Okta, Azure, or external identity links are relevant, read ../../references/docs/scim-methodology.md and inspect the small GitHound examples under ../../references/examples/githound/samples/.
3. Search ../../references/query-indexes/openhound-github.md and ../../references/examples/example-cypher.md for a saved-query starting point.
4. Inspect the referenced JSON snapshot and adapt parameters safely.
5. Preserve GH_ labels/edges, SCIM_* bridge labels/edges, and permission-inheritance path shape.
6. Separate posture checks from attack paths and list false-positive validation steps.