Openhound Github logo

Openhound Github

Organization
SpecterOps
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, 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.

Overview

PublisherSpecterOps
Repositoryskills
Skill nameopenhound-github
Stars
706
Forks
80
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by SpecterOps on GitHub. Read the source before you install it.

Installation

Install the Openhound Github AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/SpecterOps/skills/tree/main/plugins/bloodhound/skills/openhound-github
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/SpecterOps/skills.git /tmp/skills
mkdir -p .claude/skills
cp -r /tmp/skills/plugins/bloodhound/skills/openhound-github .claude/skills/openhound-github
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Openhound Github in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Openhound Github on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Openhound Github is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Common pivots

  • GitHub users/teams to repo admin/write access.
  • Branch protection bypass and dangerous branch permissions.
  • Actions policy, SHA pinning, workflow dispatch, runner, and secret exfiltration risk.
  • Secrets/variables scope exposure and secret scanning alert metadata.
  • App installations and PATs with broad repository access.
  • GitHub OIDC to Azure federated identity credentials.
  • External identities without SCIM and SCIM-provisioned identities mapped to GitHub users/teams.

Output

Use the shared output contract from $bloodhound-query and include GitHub-specific caveats such as enterprise/org coverage, Actions settings collection, SAML/SCIM data availability, secret metadata limitations, and linked-identity confidence.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Openhound Github AI skill do?

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, 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.

Why use Openhound Github on TypingMind?

Because you install it once and use it with any model. Openhound Github is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Openhound Github in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/SpecterOps/skills/tree/main/plugins/bloodhound/skills/openhound-github. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Openhound Github?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Openhound Github?

As many as you like. As long as a model supports skills, you can use Openhound Github with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Openhound Github AI skill free?

Yes. It is published on GitHub by SpecterOps under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇