Cette page est affichée en anglais. Une traduction française est en cours.
SkillsMay 11, 2026·2 min de lecture

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.

Prêt pour agents

Cet actif peut être lu et installé directement par les agents

TokRepo expose une commande CLI universelle, un contrat d'installation, le metadata JSON, un plan selon l'adaptateur et le contenu raw pour aider les agents à juger l'adaptation, le risque et les prochaines actions.

Native · 98/100Policy : autoriser
Surface agent
Tout agent MCP/CLI
Type
Skill
Installation
Single
Confiance
Confiance : Established
Point d'entrée
Asset
Commande CLI universelle
npx tokrepo install 1368ef7b-1ee3-42e8-86fb-c31edbb9d7b4
Introduction

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.

🙏

Source et remerciements

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

Fil de discussion

Connectez-vous pour rejoindre la discussion.
Aucun commentaire pour l'instant. Soyez le premier à partager votre avis.

Actifs similaires