pattt-readme-loader

Resolve on-disk PayloadsAllTheThings README files into payload suggestions with source metadata.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/0X6C7879/aegissec --skill pattt-readme-loader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pattt-readme-loader
Source: https://github.com/0X6C7879/aegissec/tree/main/skills/pattt-readme-loader
Command: npx skills add https://github.com/0X6C7879/aegissec --skill pattt-readme-loader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vendored PayloadsAllTheThings (PATTT) documentation is scattered across README files on disk. This skill resolves and loads the README-first content so AI agents can access structured payload knowledge for retrieval tasks and offensive‑knowledge workflows.

Core Features & Use Cases

  • On-disk README-first resolution: Reads real vendored README.md sources from disk to populate payload knowledge.
  • Context loading for prompts: Includes loaded_docs in model context to enable accurate payload suggestions.
  • Metadata-preserving suggestions: Returns candidate payloads with source_path and section_title metadata to support traceability.
  • Safety and routing rules: Enforces verification-first default policy and explicit gating for bypass/exploit suggestions; catalog routes do not replace raw reads.

Quick Start

Resolve the vendored PATTT README sources from disk and load them into the model context for payload recommendations.

Frequently Asked Questions about pattt-readme-loader

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

FAQPage Schema
How do I retrieve PayloadsAllTheThings documentation for Burp Intruder candidates?

To retrieve PayloadsAllTheThings documentation for Burp Intruder candidates, this skill resolves and loads vendored on-disk README.md sources into the model context to provide structured payload suggestions with source_path and section_title metadata.

What is the best way to load local README-first payloads for security research?

Loading local README-first payloads for security research is handled by reading real vendored PATTT README files from disk, enforcing a resolver that populates loaded_docs into context to provide accurate, traceable fuzz inputs and bypass ideas.

Does this payload retrieval approach provide source traceability for verification probes?

Yes, payload retrieval for verification probes provides source traceability by returning candidate payloads with explicit source_path and section_title metadata, ensuring every bypass idea or fuzz input maps back to its original README section.

Can I use vendored PATTT README files to generate fuzz inputs without an internet connection?

Yes, you can use vendored PATTT README files to generate fuzz inputs without an internet connection because the resolver reads real on-disk documentation sources to populate loaded_docs, enabling offline payload knowledge retrieval.

Are there limitations when using catalog routes for bypass ideas versus raw README reads?

A key limitation is that catalog routes do not replace raw reads; the resolver enforces reading real README.md sources from disk to populate loaded_docs, meaning catalog routes alone are insufficient for accurate payload retrieval.

When do I need explicit gating for exploit suggestions during payload retrieval?

Explicit gating for exploit suggestions during payload retrieval is required because the skill enforces a verification-first default policy, ensuring bypass and exploit suggestions are only provided when explicitly requested and safely routed.