target-dossier

Name: target-dossier
Availability: InStock
Author: entrovyx

Initialize and maintain persistent markdown directories for offensive security campaign data.

3|1|Updated Jul 2, 2026

Search Tags:#security #pentest #bug bounty #recon #dossier #offsec

Ready to run

npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill target-dossier

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: target-dossier
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/meta/target-dossier
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill target-dossier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the issue of fragmented offensive security data by creating a centralized, persistent dossier that tracks campaign progress, hypotheses, and evidence across multiple sessions.

Core Features & Use Cases

Persistent Campaign Tracking: Automatically initializes and updates a structured directory for target-specific data including request maps, evidence, and chain candidates.
Workflow Integration: Forces every test to attach to specific actors, objects, and states, ensuring that manual hunting remains impact-driven.
Use Case: When performing a bug bounty hunt, use this skill to initialize a dossier for a new target, allowing the agent to maintain context on discovered vulnerabilities and chain candidates throughout the entire engagement.

Quick Start

Invoke the target-dossier skill by typing /target-dossier followed by the target domain to initialize your campaign workspace.

Frequently Asked Questions about target-dossier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain persistent offensive security campaign data across multiple sessions?▼

A persistent offensive security campaign directory tracks target dossiers, evidence, and request maps across multiple manual hunting sessions. It enforces impact-driven testing by attaching data to specific actors and exploit chain candidates.

What is the best way to track bug bounty evidence and exploit chain candidates?▼

The best way to track bug bounty evidence is using a persistent dossier that structures target data, request maps, and chain candidates. This prevents fragmented findings by forcing every test to attach to specific actors, objects, and states throughout the engagement.

How do I initialize a structured directory for pentest recon and target dossiers?▼

To initialize a structured directory for pentest recon, invoke the dossier skill followed by the target domain. This automatically creates a campaign workspace with markdown files and directory hierarchies to track actors, object families, and exploit chain candidates.

Does this offensive security campaign tracker require external dependencies or APIs?▼

No external dependencies or APIs are required. The tracker operates entirely through local file system access to manage campaign-specific markdown files and directory hierarchies, ensuring your offensive security data remains self-contained and persistent.

Can I use this dossier system to track manual hunting workflows for bug bounty targets?▼

Yes, the dossier system is specifically designed to support manual hunting workflows for bug bounty targets. It tracks discovered vulnerabilities and maintains context on exploit chain candidates throughout the entire engagement by linking tests to actors and object families.

What limitations exist when managing local markdown files for offensive security campaigns?▼

The primary limitation is the strict requirement for local file system access to manage campaign-specific markdown files and directory hierarchies. It does not integrate with external APIs or cloud platforms, meaning all persistent tracking relies entirely on the local environment.