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.ptgit 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.pt)<a href="https://agentmods.dev/commands/druide67/asiai/config.pt"><img src="https://agentmods.dev/badge/commands/druide67/asiai/config.pt.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.00572 |
| Opus 5 | $0.00014 | $0.00286 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
config.pt 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 5d 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.
What it actually says
asiai config
Gerencie configuração persistente de motores. Motores descobertos pelo asiai detect são automaticamente salvos em ~/.config/asiai/engines.json para detecção mais rápida nas próximas vezes.
Uso
asiai config show # Mostrar motores conhecidos
asiai config add <engine> <url> [--label NAME] # Adicionar motor manualmente
asiai config remove <url> # Remover um motor
asiai config reset # Limpar toda a configuração
Subcomandos
show
Exibe todos os motores conhecidos com URL, versão, fonte (auto/manual) e timestamp do último contato.
$ 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
Registre manualmente um motor em uma porta não padrão. Motores manuais nunca são removidos automaticamente.
asiai config add omlx http://localhost:8800 --label desktop
asiai config add ollama http://192.0.2.10:11434 --label remote
remove
Remova uma entrada de motor pela URL.
asiai config remove http://localhost:8800
reset
Apaga todo o arquivo de configuração. O próximo asiai detect vai redescobrir motores do zero.
Como funciona
O arquivo de configuração armazena motores descobertos durante a detecção:
- Entradas auto (
source: auto): criadas automaticamente quandoasiai detectencontra um novo motor. Removidas após 7 dias de inatividade. - Entradas manuais (
source: manual): criadas viaasiai config add. Nunca removidas automaticamente.
A cascata de detecção em 3 camadas do asiai detect usa esta configuração como Camada 1 (mais rápida), seguida por varredura de portas (Camada 2) e detecção de processos (Camada 3). Veja detect para detalhes.
Localização do arquivo de configuração
~/.config/asiai/engines.json
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.
- 5d ago First seen · 67 lines · 28 tokens per session scan A 4134172e9603
config.pt is a command published in the GitHub repository druide67/asiai (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 28 tokens to every session and 572 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-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.
/opsx-propose
Propose a new change - create it and generate all artifacts in one step.