mythic-c2-readonly

Query Mythic C2 operation data with read-only access.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill mythic-c2-readonly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mythic-c2-readonly
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/mythic-c2-readonly/skills/mythic-c2-readonly
Command: npx skills add https://github.com/dreadnode/capabilities --skill mythic-c2-readonly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mythic, gql, pydantic, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the risk of accidental state modification when reviewing Mythic C2 operation data, allowing security analysts and red team operators to safely examine collected evidence like callbacks, task history, credentials, and files without executing commands or disrupting active operations.

Core Features & Use Cases

  • Comprehensive Read-Only Data Access: Query all core Mythic data types including callbacks, task output, credentials, files, artifacts, keylogs, screenshots, process listings, file browser entries, and Windows token captures.
  • Flexible Search and Filtering: Use cross-type search to find data across all categories, or filter results by callback ID, host, path, or active status to narrow down relevant information.
  • Use Case: During a post-operation review, use this Skill to pull all credentials collected during a red team engagement, cross-reference them with associated task output, and export the data for reporting without risking accidental command execution on live agent callbacks.

Quick Start

Use the mythic-c2-readonly skill to retrieve a list of all active callbacks in the current Mythic operation, including their host, associated user, and last check-in timestamp.

Frequently Asked Questions about mythic-c2-readonly

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

FAQPage Schema
How do I query Mythic C2 operation data without risking state changes to active callbacks?

You can query Mythic C2 data safely by using a read-only interface that retrieves callbacks, task history, and credentials without executing commands or modifying agent state. This prevents accidental disruption of active red team operations during post-operation reviews.

Can I search across all Mythic C2 data types at once to find specific artifacts?

Yes, cross-type search allows you to find data across all Mythic categories simultaneously. You can search for artifacts, credentials, keylogs, and screenshots across the entire operation dataset without needing separate queries for each data type.

How do I retrieve large task outputs and files from Mythic without timing out?

Large task responses and files are handled through paginated output. This approach breaks down extensive C2 task data into manageable pages, ensuring stable retrieval of post-exploitation collection data like process listings and file browser entries.

What Mythic C2 data types can I filter by callback ID or host?

You can filter all core Mythic data types by callback ID, host, or path. This includes filtering task history, credentials, files, keylogs, screenshots, process listings, file browser entries, and Windows tokens to narrow down relevant operation data.

Does this read-only Mythic approach work for post-exploitation reporting?

Yes, read-only Mythic access is designed for post-operation reporting. Security analysts can pull all collected credentials and task output, cross-reference the data, and export it for documentation without risking accidental command execution on live agents.