agents-md-author

Generate or maintain concise AGENTS.md routing maps for Codex.

3|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill agents-md-author-pax-k
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agents-md-author
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/agents-md-author
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill agents-md-author-pax-k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps create or maintain concise, high-signal AGENTS.md for coding agents, addressing the need for clear instructions without overwhelming project documentation.

Core Features & Use Cases

  • Concise Instructions: Generate or maintain AGENTS.md under 120 lines, ensuring it's a routing map for Codex rather than a comprehensive knowledge dump.
  • Scalable Documentation: Maintain project-specific constraints while keeping the main file concise, with detailed knowledge in separate documents.
  • Standard Commands: Link to standard commands like 'dev', 'lint', 'typecheck', 'test', 'build', and 'validate'.

Quick Start

Generate a minimal AGENTS.md for your project with agents-md-author.

Frequently Asked Questions about agents-md-author

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

FAQPage Schema
How do I generate an AGENTS.md file for coding agents?

An AGENTS.md file provides a routing map for Codex and other coding agents to navigate project constraints. It links standard commands like dev, lint, typecheck, and build while keeping detailed knowledge in separate documents to avoid overwhelming the main file.

How do I keep AGENTS.md concise for Codex without losing project constraints?

You can scale AGENTS.md documentation by keeping the main file concise as a routing map and moving detailed knowledge to separate documents. This maintains project-specific constraints for coding agents while preventing the primary file from becoming a comprehensive knowledge dump.

What is the best way to structure project documentation for coding agents?

AGENTS.md links to standard commands including dev, lint, typecheck, test, build, and validate. These links provide coding agents with a clear routing map to execute standard project workflows without loading comprehensive knowledge into the main file.

Why should AGENTS.md be a routing map instead of a comprehensive knowledge dump?

AGENTS.md should be a routing map instead of a knowledge dump because coding agents require high-signal instructions without overwhelming project documentation. Keeping the file under 120 lines ensures clear agent instructions while detailed knowledge remains in separate, scalable documents.