post-discovery

Enumerate access scope and impact of validator-confirmed credentials via read-only provider probes.

4|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Ap6pack/outrider-recon --skill post-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-discovery
Source: https://github.com/Ap6pack/outrider-recon/tree/main/skills/post-discovery
Command: npx skills add https://github.com/Ap6pack/outrider-recon --skill post-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps authorized security teams determine the scope and impact of validated credentials without immediately modifying systems, creating resources, or sending messages.

Core Features & Use Cases

  • Provider-Specific Enumeration: Assess AWS IAM, GitHub PAT, Slack, Postman, Anthropic, OpenAI, and other credential scopes through read-only workflows.
  • JWT Triage: Decode claims, identify privilege indicators, and assess algorithm-related risks under explicit authorization.
  • Evidence-Backed Reporting: Record account identity, permissions, accessible resources, detectability, and timestamps for downstream severity analysis.
  • Safety Gates: Require validator confirmation and explicit Rules of Engagement authorization before authenticated enumeration begins.
  • Use Case: After a validator confirms a GitHub token is live, use this Skill to document its scopes, accessible repositories, organization memberships, and workflow-secret metadata without retrieving secret values.

Quick Start

Ask the post-discovery skill to enumerate the authorized scope of a validator-confirmed credential and produce an evidence-backed report.

Frequently Asked Questions about post-discovery

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

FAQPage Schema
How do I enumerate access scope for validated AWS IAM or GitHub PAT credentials without modifying resources?

Enumerate validated credential access scope safely by running read-only provider probes that document account identity, permissions, and accessible resources without unauthorized modification, data retrieval, or sending messages.

What is credential enumeration in a post-discovery security assessment workflow?

Credential enumeration in a post-discovery workflow is the process of mapping the access scope and impact of validated credentials using read-only provider probes to record permissions and accessible resources for severity analysis.

Can I triage JWT claims and algorithm-related risks using read-only reconnaissance?

Yes, you can triage JWT claims by decoding them to identify privilege indicators and assessing algorithm-related risks under explicit Rules of Engagement authorization without unauthorized data retrieval.

Do I need explicit authorization and validator confirmation before assessing API key scope?

Yes, assessing API key scope requires validator confirmation confirming the credential is live, explicit Rules of Engagement authorization, and policy-gated execution before any authenticated read-only enumeration begins.

What's the best way to document Slack or Postman credential permissions for downstream severity analysis?

The best way to document credential permissions is through evidence-backed reporting that records account identity, accessible resources, detectability, and timestamps during your authorized read-only enumeration.

When should I not use read-only reconnaissance for credential triage?

You should not use read-only reconnaissance when validator confirmation is absent, explicit Rules of Engagement authorization is missing, or policy-gated execution constraints are not established for the target provider.