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.jagit 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.ja)<a href="https://agentmods.dev/commands/druide67/asiai/config.ja"><img src="https://agentmods.dev/badge/commands/druide67/asiai/config.ja.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.00033 | $0.00689 |
| Opus 5 | $0.00016 | $0.00345 |
| Sonnet 5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
config.ja 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- config.ko — 100% identical, 36 lines differ
What it actually says
asiai config
永続的なエンジン設定を管理します。asiai detect で検出されたエンジンは、次回の検出を高速化するために ~/.config/asiai/engines.json に自動保存されます。
使用方法
asiai config show # 既知のエンジンを表示
asiai config add <engine> <url> [--label NAME] # エンジンを手動追加
asiai config remove <url> # エンジンを削除
asiai config reset # すべての設定をクリア
サブコマンド
show
URL、バージョン、ソース（auto/manual）、最終確認タイムスタンプと共にすべての既知エンジンを表示。
$ 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
非標準ポートのエンジンを手動登録。手動エンジンは自動プルーニングされません。
asiai config add omlx http://localhost:8800 --label desktop
asiai config add ollama http://192.0.2.10:11434 --label remote
remove
URLでエンジンエントリを削除。
asiai config remove http://localhost:8800
reset
設定ファイル全体を削除。次の asiai detect でエンジンをゼロから再検出します。
仕組み
設定ファイルは検出時に発見されたエンジンを保存します：
- Autoエントリ（
source: auto）：asiai detectが新しいエンジンを見つけたときに自動作成。7日間非アクティブ後にプルーニング。 - Manualエントリ（
source: manual）：asiai config addで作成。自動プルーニングされません。
asiai detect の3層検出カスケードはこの設定をレイヤー1（最速）として使用し、続いてポートスキャン（レイヤー2）とプロセス検出（レイヤー3）を行います。詳細は detect を参照。
設定ファイルの場所
~/.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 · 33 tokens per session scan A bdc15843008b
config.ja is a command published in the GitHub repository druide67/asiai (11 stars, last pushed 6d ago), licensed Apache-2.0. It adds 33 tokens to every session and 689 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-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.