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.degit 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.de)<a href="https://agentmods.dev/commands/druide67/asiai/config.de"><img src="https://agentmods.dev/badge/commands/druide67/asiai/config.de.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 | $0.00030 | $0.00589 |
| Opus 5 | $0.00015 | $0.00295 |
| Sonnet 5 | $0.00006 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
config.de 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 4d 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
Persistente Engine-Konfiguration verwalten. Von asiai detect entdeckte Engines werden automatisch in ~/.config/asiai/engines.json gespeichert, um nachfolgende Erkennung zu beschleunigen.
Verwendung
asiai config show # Bekannte Engines anzeigen
asiai config add <engine> <url> [--label NAME] # Engine manuell hinzufügen
asiai config remove <url> # Eine Engine entfernen
asiai config reset # Gesamte Konfiguration löschen
Unterbefehle
show
Zeigt alle bekannten Engines mit URL, Version, Quelle (auto/manual) und letztem Erkennungszeitpunkt.
$ 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
Engine manuell auf einem nicht standardmäßigen Port registrieren. Manuelle Engines werden nie automatisch entfernt.
asiai config add omlx http://localhost:8800 --label desktop
asiai config add ollama http://192.0.2.10:11434 --label remote
remove
Einen Engine-Eintrag nach URL entfernen.
asiai config remove http://localhost:8800
reset
Die gesamte Konfigurationsdatei löschen. Der nächste asiai detect wird Engines von Grund auf neu erkennen.
Funktionsweise
Die Konfigurationsdatei speichert während der Erkennung entdeckte Engines:
- Auto-Einträge (
source: auto): Werden automatisch erstellt, wennasiai detecteine neue Engine findet. Nach 7 Tagen Inaktivität bereinigt. - Manuelle Einträge (
source: manual): Überasiai config adderstellt. Werden nie automatisch bereinigt.
Die 3-Schichten-Erkennungskaskade in asiai detect nutzt diese Konfiguration als Schicht 1 (schnellste), gefolgt von Port-Scan (Schicht 2) und Prozesserkennung (Schicht 3). Siehe detect für Details.
Speicherort der Konfigurationsdatei
~/.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.
- 4d ago First seen · 67 lines · 30 tokens per session scan A f9b727f874ab
config.de is a command published in the GitHub repository druide67/asiai (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 30 tokens to every session and 589 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-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.