| 1 | # Hacker Agent Profile DOX |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | - Own the bundled cyber security and penetration testing specialist profile. |
| 6 | - Keep security-audit behavior scoped to this profile instead of default agent behavior. |
| 7 | |
| 8 | ## Ownership |
| 9 | |
| 10 | - `agent.yaml` owns title, description, and delegation context for security work. |
| 11 | - `prompts/` owns security-specific prompt overrides when present. |
| 12 | |
| 13 | ## Local Contracts |
| 14 | |
| 15 | - Keep the profile focused on authorized security analysis, vulnerability research, and defensive audit tasks. |
| 16 | - Do not add secrets, target-specific credentials, or local environment assumptions. |
| 17 | - Preserve the framework tool-call contract and safety expectations. |
| 18 | |
| 19 | ## Work Guidance |
| 20 | |
| 21 | - Keep security instructions operational and bounded to legitimate testing contexts. |
| 22 | - Coordinate broad safety changes with core prompts and relevant tests. |
| 23 | |
| 24 | ## Verification |
| 25 | |
| 26 | - Manually inspect `agent.yaml` for valid YAML after edits. |
| 27 | - Run prompt/profile tests when changing profile discovery or security prompt behavior. |
| 28 | |
| 29 | ## Child DOX Index |
| 30 | |
| 31 | No child DOX files. |