Esta página se muestra en inglés. Una traducción al español está en curso.
SkillsMay 11, 2026·2 min de lectura

Security Investigator — Copilot Security Investigation Kit

Security Investigator is an investigation system combining Copilot/Agent Skills with security tooling to triage suspicious changes and threats faster.

Listo para agents

Instalación lista para agent

Este activo puede instalarse después de elegir el runtime, revisar el plan y ejecutar el comando correspondiente.

Native · 98/100Política: permitir
Superficie agent
Cualquier agent MCP/CLI
Tipo
Skill
Instalación
Single
Confianza
Confianza: Established
Entrada
Asset
Comando de instalación directa
npx -y tokrepo@latest install 1368ef7b-1ee3-42e8-86fb-c31edbb9d7b4 --target codex

Ejecutar después de confirmar el plan con dry-run.

Introducción

Security Investigator is an investigation system combining Copilot/Agent Skills with security tooling to triage suspicious changes and threats faster.

  • Best for: Security teams prototyping Copilot-assisted investigations with a repeatable repo workflow
  • Works with: Python environment + VS Code + external security services; includes templates for MCP and config files
  • Setup time: 35 minutes

Practical Notes

  • Setup time ~35 minutes (clone + venv + requirements + config templates)
  • README highlights 25 specialized Agent Skills as building blocks for investigations
  • GitHub stars + forks (verified): see Source & Thanks

For teams adopting this repo, treat it like a playbook:

  • Start with one investigation workflow (e.g., secrets triage) and harden it.
  • Lock down tokens/credentials and avoid storing them in repo files.
  • Add an audit trail: record what prompts ran, what tools were called, and what evidence was collected.

Because investigation systems can touch sensitive data, run a dry “safe mode” first: use dummy credentials and verify the workflow never calls destructive actions by default.

FAQ

Q: Is this only for Copilot? A: The project is designed around Copilot/Agent Skills, but the workflows and prompts can inspire similar setups in other agent environments.

Q: How do I avoid leaking secrets? A: Keep tokens in env/secret stores, sanitize logs, and review generated artifacts before sharing.

Q: What is a safe first milestone? A: One end-to-end workflow that produces repeatable output with dummy credentials and no destructive calls.

🙏

Fuente y agradecimientos

Source: https://github.com/SCStelz/security-investigator > License: MIT > GitHub stars: 198 · forks: 51

Discusión

Inicia sesión para unirte a la discusión.
Aún no hay comentarios. Sé el primero en compartir tus ideas.

Activos relacionados