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

- Skill: `specterops/openhound-development` (Agent Skill, multi-file: 13 files)
- Install (CLI): `npx get-skill add specterops/openhound-development`
- Raw SKILL.md: https://api.skillmd.com/api/skills/specterops/openhound-development/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: specterops (https://skillmd.com/u/specterops)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/specterops/openhound-development

---


# OpenHound Development Skill

Use this skill for any OpenHound collector task.

## Critical Rules (Always apply)


1. Read `references/architecture.md` before editing collector code. This includes important standards and best practices for OpenHound collector development that are not repeated in the reference docs.
2. Based on the requested task, select the matching reference from the routing table. These contain specific rules and examples for different types of collector work.
3. For broad collector work, or when creating a new collector, read `references/plan-collector.md`.
4. Important: Before finishing collector and graph behavior changes read `references/validate-extension.md`.

### Route By Task

| Task | Reference |
|---|---|
| Plan a new collector from API docs, sample responses, or requirements | `references/plan-collector.md` |
| Define graph base classes, common properties, node IDs, or edge properties | `references/graph-schema.md` |
| Register `collect`, `preproc`, `convert`, metadata, or entry points | `references/register-extension.md` |
| Implement API clients, auth, DLT resources, transformers, or secrets | `references/source-collection.md` |
| Implement multiple authentication options with DLT configspec unions | `references/multi-auth.md` |
| Add or modify models, node assets, edge assets, kind constants, or exports | `references/add-asset.md` |
| Add DuckDB transforms, lookup methods, lookup registration, or `self._lookup` usage | `references/preproc-lookup.md` |
| Validate collector changes before finishing | `references/validate-extension.md` |

### Routing Rules

- If the task touches multiple areas, read every matching reference.
- If adding or changing collector behavior, always read `references/validate-extension.md` before finishing.
- If the task involves a new collector or broad redesign, start with `references/plan-collector.md`.
- If a collector supports more than one authentication method, read `references/multi-auth.md` and `references/source-collection.md`.
- If models use `self._lookup`, also read `references/preproc-lookup.md` and `references/register-extension.md`.
- If adding a new collected resource, usually read `references/source-collection.md`, `references/add-asset.md`, and `references/validate-extension.md`.

