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.
git clone --depth 1 https://github.com/algolia/skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/algolia/skills/cli-setup)<a href="https://agentmods.dev/commands/algolia/skills/cli-setup"><img src="https://agentmods.dev/badge/commands/algolia/skills/cli-setup/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/algolia/skills/cli-setup"><img src="https://agentmods.dev/badge/commands/algolia/skills/cli-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00012 | $0.00487 |
| Opus 5.5 | $0.00005 | $0.00195 |
| Sonnet 5.5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade B, and why
cli-setup scanned grade B with 1 finding 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 1mo 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
echo "deb [trusted=yes] https://algolia.github.io/cli/deb/ /" | sudo tee /etc/apt/sources.list.d/algolia-cli.list What it actually says
Algolia CLI Setup
Guide the user through installing the Algolia CLI and configuring their credentials.
Step 1: Check if the CLI is installed
Run:
algolia --version
- If the command succeeds, skip to Step 3.
- If the command fails (command not found), proceed to Step 2.
Step 2: Install the CLI
Detect the platform and install:
macOS (Homebrew):
brew install algolia/algolia-cli/algolia
Linux (Debian/Ubuntu):
echo "deb [trusted=yes] https://algolia.github.io/cli/deb/ /" | sudo tee /etc/apt/sources.list.d/algolia-cli.list
sudo apt update && sudo apt install algolia
Other platforms: Direct the user to https://www.algolia.com/doc/tools/cli/get-started for download options.
After installation, verify:
algolia --version
Step 3: Check for existing profiles
Run:
algolia profile list
- If profiles exist, ask the user if they want to use an existing profile or create a new one.
- If no profiles exist (or the command shows an empty list), proceed to Step 4.
Step 4: Create a profile
Ask the user for:
- Application ID — Found in Algolia Dashboard → Settings → API Keys
- Admin API key — Same location. Needed for write operations.
Then run:
algolia profile add --name "default" --app-id "<APP_ID>" --api-key "<API_KEY>" --default
Important: Always provide all three flags to avoid interactive prompts.
Step 5: Verify the connection
Run:
algolia indices list
- If indices are listed, setup is complete. Tell the user they're ready to go.
- If an error occurs, check:
- Invalid API key → ask user to double-check credentials
- Network error → ask user to check connectivity
- No indices → that's fine, the connection works but the app has no indices yet
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.
- 1mo ago First seen · 83 lines · 12 tokens per session scan B e65c6f5fa011
cli-setup is a command published in the GitHub repository algolia/skills (12 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 487 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
screenshot
Screenshot a URL or document and read it visually.
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.