Agents
Give coding agents stable Argus documentation plus portable setup and research skills.
Argus exposes its documentation and two focused skills in formats an agent can
fetch directly. Use argus-setup to operate a host and argus-research to turn
an existing instance into sourced context without changing collection.
Documentation interfaces
| Interface | Use |
|---|---|
/llms.txt | Compact index of every documentation page with absolute canonical URLs. |
/llms-full.txt | Processed Markdown for the complete handbook. |
/docs/<path>.md | Processed Markdown for one docs page, such as /docs/quick-start.md. |
/skill/SKILL.md | The current portable argus-setup skill entry file. |
/skill/argus-skill.zip | Deterministic archive containing argus-setup, its license, and references. |
/skill/research/SKILL.md | The portable argus-research entry file. |
/skill/argus-research.zip | Deterministic research-skill archive with API, traversal, and provenance references. |
Install the setup skill
Download and extract the archive into your client's skills directory. Both
Codex and Claude-compatible clients discover a directory containing
SKILL.md; the archive already has the required argus-setup/ top-level
directory.
curl -fsSLo /tmp/argus-skill.zip https://argus.gpsxtre.me/skill/argus-skill.zip
unzip -o /tmp/argus-skill.zip -d ~/.codex/skillsFor Claude Code, use its user skills directory instead:
curl -fsSLo /tmp/argus-skill.zip https://argus.gpsxtre.me/skill/argus-skill.zip
unzip -o /tmp/argus-skill.zip -d ~/.claude/skillsRestart or refresh the client if it does not discover newly installed skills. Inspect the entry file before installation when your client or organization requires a review step.
Install the research skill
Install this alongside setup when an agent needs to query stored records, inspect X reply samples, traverse configured FxEmbed/SearXNG primitives, and write briefs with honest coverage language.
curl -fsSLo /tmp/argus-research.zip https://argus.gpsxtre.me/skill/argus-research.zip
unzip -o /tmp/argus-research.zip -d ~/.codex/skillsUse ~/.claude/skills instead for Claude Code. API tokens belong in the
agent's runtime environment. The research skill never instructs an agent to
place a bearer token in a URL, transcript, or report.
CLI and safety boundaries
Use --json whenever an agent reads CLI output. Successful responses use the
versioned envelope {"contractVersion":1,"ok":true,"data":{}}; failures
contain error.code, error.message, and sometimes error.recovery. Treat
the live CLI schema, help, plan, and JSON result as authority rather than
recreating deployment logic in a chat response.
Read-only inspection is distinct from change. Before onboarding, repair, update, configuration apply, or any operation that can change a host or an optional Cloudflare account, inspect the CLI plan, explain it, and obtain explicit approval at the CLI confirmation boundary. A dry run does not authorize its later mutating form.
Secrets must stay in hidden CLI prompts or approved local secret storage, never in chat, an answers file, a command argument, or a transcript. The CLI redacts known secret values in its output, but agents must still avoid echoing, persisting, or forwarding credentials.
For a failed health check or command, run argus doctor --json, report its
component/code/message, and follow a returned recovery or log command exactly.
If recovery is missing, unclear, outside approval, or requests new authority,
stop and ask the user. Do not edit Compose files, deployment state, backups,
managed settings, or secret files directly; the setup skill
contains the detailed routing rules.