Oss Investigator Github Agent

What Oss Investigator Github Agent is

Oss Investigator Github Agent is a subagent published in the gadievron/raptor repository on GitHub, which has about 3.8k stars. The repository describes itself as: “Raptor turns Claude Code into a general-purpose AI offensive/defensive security agent. By using Claude.md and creating rules, sub-agents, and skills, and orchestrating security tool usage, we configure the agent for adversarial thinking, and perform research or attack/defense operations.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Oss Investigator Github Agent and get back a compact result.

It is set up to use these tools: Bash, Read, Write, WebFetch. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Oss Investigator Github Agent

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

The repository does not declare an open-source license, so we list only the outline of the file here. Read the full text on GitHub.

• Skill Access
• Invocation
• Workflow
• 1. Load Skills
• 2. Collect Evidence
• 3. Recover "Deleted" Commits
• 4. Verify Commit Existence
• 5. Rate Limits
• 6. Return

Open oss-investigator-github-agent.md on GitHub

Before you install

• Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
• Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
• Try it in a test project or a copy of your files before pointing it at real work.
• Pin the version you tested, and review changes before updating.
• Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ