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.
npx agentmods add commands/archastro/archagents/installgit clone --depth 1 https://github.com/ArchAstro/archagentsWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00006 | $0.00442 |
| Opus 5 | $0.00003 | $0.00221 |
| Sonnet 5 | $0.00001 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade C, and why
install scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/ArchAstro/archagents/main/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: ["Bash(archagent:*)", "Bash(brew:*)", "Bash(curl:*)", "Bash(bash:*)", "Bash(sh:*)", "Bash(pwsh:*)", "Bash(powershell:*)"] What it actually says
Install ArchAgent CLI
Install or upgrade the public archagent binary from Homebrew or GitHub Releases.
Workflow
-
Check whether the CLI is already installed:
archagent --versionIf this succeeds, record the version.
-
If the CLI is present and the user didn't ask to upgrade, confirm the version and stop.
-
If the CLI is missing or the user asked to upgrade, install it using the public distribution path:
- On macOS, if Homebrew is available:
If the formula is already installed, run:brew install ArchAstro/tools/archagentbrew upgrade ArchAstro/tools/archagent - On Linux or macOS without Homebrew:
curl -fsSL https://raw.githubusercontent.com/ArchAstro/archagents/main/install.sh | bash - On Windows PowerShell:
irm https://raw.githubusercontent.com/ArchAstro/archagents/main/install.ps1 | iex
- On macOS, if Homebrew is available:
-
Verify installation:
archagent --version -
On failure, help troubleshoot the public install path:
- Missing
brewis expected on Linux and some macOS setups; fall back toinstall.sh. Permission deniedusually means they need--install-diror a user-writable target directory.command not found: archagentafter install usually means the install directory is not onPATH.- Release download failures usually mean the target release asset has not been published yet.
- Missing
-
On success, tell the user the CLI is ready and suggest
/archagents:auth.
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.
- 2d ago First seen · 50 lines · 6 tokens per session scan C 45590fa80bf5
install is a command published in the GitHub repository ArchAstro/archagents (5 stars, last pushed 16d ago), licensed MIT. It adds 6 tokens to every session and 442 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
test-review
Review DataHub smoke and integration tests for standards compliance and quality.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.