Use git-hound when the real task is external secret exposure hunting across public GitHub, especially before incident response, key rotation, or partner notification work. Its scope boundary is crisp: run GitHub dork based searches, inspect matches with contextual detection and history digging, and surface likely credential leaks for follow-up. That makes it skill-shaped and distinct from a generic security product card. The operator is invoking a focused reconnaissance workflow, not browsing a general security platform or SDK.