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/rivolink/rl-analyzer/askinggit clone --depth 1 https://github.com/RivoLink/rl-analyzerWhat 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.00033 | $0.01002 |
| Opus 5 | $0.00016 | $0.00501 |
| Sonnet 5 | $0.00007 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
asking 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 48 lines · 33 tokens per session scan A a2427c2b97d4
asking is a command published in the GitHub repository RivoLink/rl-analyzer (1 stars, last pushed 4mo ago), with no licence file. It adds 33 tokens to every session and 1,002 once invoked, about $0.0002 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.
Other commands, from other repositories
browser
Inspect and control the current AO session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies, navigation state, and WebContentsView; the runtime remains usable while the Browser panel is hidden. Tabs in this worker share an ephemeral browser profile, while…
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
import
Import reads the legacy Agent Orchestrator flat-file store (/.agent-orchestrator) read-only and ports its projects and per-project settings into the rewrite database. Legacy files are never modified, and a re-run skips rows that already exist, so it is safe to run more than once. The daemon must be stopped before…
orchestrator
Command "orchestrator" from Untrivial-ai/agent-orchestrator, covering ao orchestrator, syntax, subcommands, ao orchestrator ls and examples.
start
Fetch (if needed) and open the Agent Orchestrator desktop app. The desktop app owns the daemon, state, and updates. ao start no longer runs a daemon: it resolves the installed app (or downloads the latest release), opens it, and exits.
doctor
Run local AO health checks. Use this to diagnose setup problems or verify the environment is correctly configured.