ai-ready-docs

Documentation guidance for Argos, a service that checks visual changes in websites and applications using screenshots. It describes Markdown pages, searchable indexes, and a read-only documentation connection for AI assistants.

In plain words
What is it for?
Use it when an agent needs to discover, search, or read Argos documentation.
Why use it?
It gives coding agents machine-readable sources so they can find and read Argos documentation more reliably than scraping normal web pages.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/argos-ci/docs/ai-ready-docs
Clone the repo
git clone --depth 1 https://github.com/argos-ci/docs
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 384 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00384
Opus 5 $0.00014 $0.00192
Sonnet 5 $0.00005 $0.00077
Haiku 4.5 $0.00003 $0.00038

Measured 2d ago against content hash 0a9726f01b49, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ai-ready-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs/agents/ai-ready-docs.md · 41 lines

What it actually says

AI-ready docs

This documentation is published with GitBook, which exposes AI-friendly outputs for every page. Point your agent at these endpoints instead of letting it scrape HTML.

Markdown for every page

Append .md to any page URL to get its raw Markdown:

https://argos-ci.com/docs/agents/mcp-server.md

Site indexes: llms.txt and llms-full.txt

Docs MCP server

The documentation also exposes its own read-only MCP server, so MCP-compatible tools can search and read these docs directly:

https://argos-ci.com/docs/~gitbook/mcp

For example, with Claude Code:

claude mcp add --transport http argos-docs https://argos-ci.com/docs/~gitbook/mcp

{% hint style="info" %} This docs MCP server answers questions about Argos from the documentation. To let an agent act on your Argos account — list builds, review changes, post comments — connect it to the Argos MCP server instead. {% endhint %}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 41 lines · 27 tokens per session scan A 0a9726f01b49

Subscribe to this mod's changes

ai-ready-docs is an agent published in the GitHub repository argos-ci/docs (5 stars, last pushed 14d ago), licensed MIT. It adds 27 tokens to every session and 384 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.