Agentic tools 1.3.0

Agentic tools 1.3.0 generate a complete publication bundle: agentic.json, agentic.txt, README.md, and LISTING.md. Enter a public website URL to discover its documentation, APIs, llms.txt, and advertised agent connections, then download the four files or copy each one.

• TXT 1.2 includes clearly labeled descriptions and web addresses for Agentic (ruagentic.org), the open file convention and tools, and RUAGENTIC (ruagentic.com), the official Agentic directory for agentic AI MCP servers and tools.
• Generated README and listing text include service details, discovered documentation and connection links, file publication instructions, and both project references. They are portable copy for directory submissions, not evidence that a service is listed or endorsed.
• Audit report 3 adds successful, partial, and failed publication results, README link checks, and concrete fixes. Supply a public raw README URL when documentation lives elsewhere. The checker never follows README destinations or executes advertised tools.
• CLI bundle creates four files from existing JSON. audit --readme URL --publication enforces a complete publication; default audit exit semantics remain compatible. Hosted MCP and A2A accept the optional README URL.
• Action Profile 1.0.0 and Site Profile 1.1.0 JSON contracts remain unchanged. Legacy TXT 1.0/1.1 remain accepted; text --legacy reproduces them, while current generation uses TXT 1.2.
• Generator downloads, audit results, saved-report presentation, specifications, CLI docs, and agent skill are updated together.

npm install -g ruagentic@1.3.0
agentic discover https://your-site.com --out agentic-files
agentic bundle agentic.json --out publication-files
agentic audit https://your-site.com --readme https://raw.example/README.md --publication

Validation: 73 tests passed without skips, including real HTTP/SQLite/PostgreSQL recovery and official protocol clients, README failure/partial/success outcomes, misleading markup, input restrictions, bounded parsing, and no-overwrite CLI behavior. Type checking, all thirteen exported pages and local downloads, and a clean installed package's JSON/TXT/bundle/MCP checks passed. Repository-wide lint remains outside the passing checks because of existing generated-validator, shared-UI and source/test rule violations.

The audit's legacy valid field covers profile/API checks; use publication.status or CLI --publication to require matching TXT and README. A successful file audit does not certify runtime behavior, directory availability, listing acceptance, or every statement in README prose.

Generate · Audit · Publication specification