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/druide67/asiai/config.esgit clone --depth 1 https://github.com/druide67/asiaiWrote 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/druide67/asiai/config.es)<a href="https://agentmods.dev/commands/druide67/asiai/config.es"><img src="https://agentmods.dev/badge/commands/druide67/asiai/config.es.svg" alt="Measured on agentmods" 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.00028 | $0.00579 |
| Opus 5 | $0.00014 | $0.00290 |
| Sonnet 5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
config.es 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
asiai config
Gestiona la configuración persistente de motores. Los motores descubiertos por asiai detect se guardan automáticamente en ~/.config/asiai/engines.json para una detección posterior más rápida.
Uso
asiai config show # Mostrar motores conocidos
asiai config add <engine> <url> [--label NAME] # Añadir motor manualmente
asiai config remove <url> # Eliminar un motor
asiai config reset # Borrar toda la configuración
Subcomandos
show
Muestra todos los motores conocidos con su URL, versión, origen (auto/manual) y última marca de tiempo.
$ asiai config show
Known engines (3):
ollama v0.17.7 at http://localhost:11434 (auto) last seen 2m ago
lmstudio v0.4.6 at http://localhost:1234 (auto) last seen 2m ago
omlx v0.9.2 at http://localhost:8800 [mac-mini] (manual) last seen 5m ago
add
Registra manualmente un motor en un puerto no estándar. Los motores manuales nunca se eliminan automáticamente.
asiai config add omlx http://localhost:8800 --label desktop
asiai config add ollama http://192.0.2.10:11434 --label remote
remove
Elimina una entrada de motor por URL.
asiai config remove http://localhost:8800
reset
Elimina todo el archivo de configuración. El siguiente asiai detect redescubrirá los motores desde cero.
Cómo funciona
El archivo de configuración almacena los motores descubiertos durante la detección:
- Entradas automáticas (
source: auto): creadas automáticamente cuandoasiai detectencuentra un nuevo motor. Se eliminan después de 7 días de inactividad. - Entradas manuales (
source: manual): creadas medianteasiai config add. Nunca se eliminan automáticamente.
La cascada de detección de 3 capas de asiai detect usa esta configuración como Capa 1 (la más rápida), seguida del escaneo de puertos (Capa 2) y la detección de procesos (Capa 3). Consulta detect para más detalles.
Ubicación del archivo de configuración
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.
- 6d ago First seen · 67 lines · 28 tokens per session scan A c9e33eed9f03
config.es is a command published in the GitHub repository druide67/asiai (11 stars, last pushed 7d ago), licensed Apache-2.0. It adds 28 tokens to every session and 579 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-30.
Other commands, from other repositories
perfup
Autonomous performance optimization: research, PoC, benchmark, implement, review, PR.
integrate-pipeline
Integrate a new document parsing pipeline into ParseBench: $ARGUMENTS.
netllm-connect
Wire Cursor, Claude Code, Codex, or Honcho to the local netllm router.
netllm-setup
First-time netllm install from this repo (uv sync, init, discover, verify).
netllm-swarm
Configure multi-machine LAN mesh for netllm (mDNS, peers, gateway).
/opsx-explore
Enter explore mode - think through ideas, investigate problems, clarify requirements.