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 skills/lwtlong/aida/aida-uinpx skills add LWTlong/aida --skill aida-uigit clone --depth 1 https://github.com/LWTlong/aidaWrote 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/skills/lwtlong/aida/aida-ui)<a href="https://agentmods.dev/skills/lwtlong/aida/aida-ui"><img src="https://agentmods.dev/badge/skills/lwtlong/aida/aida-ui.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.00048 | $0.00531 |
| Opus 5 | $0.00024 | $0.00266 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
aida-ui 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
AIDA UI
Goal
检查本地是否安装了 aida npm 包，没有则引导用户安装，最终给出启动命令。
Steps
-
检查是否已安装：运行
npx --no aida --version 2>/dev/null || echo "NOT_INSTALLED"- 有版本号输出 → 已安装，跳到步骤 3
- 输出
NOT_INSTALLED→ 未安装，继续步骤 2
-
引导安装：告知用户需要安装
aidanpm 包才能使用 Dashboard，询问是否安装：- 用 AskUserQuestion 确认：
header: "安装 aida"question: "Dashboard 需要本地安装 aida npm 包，是否现在安装？"- 选项 A "全局安装（推荐）" —
npm install -g aida --registry https://registry.npmjs.org，任意目录可用 - 选项 B "项目内安装" —
npm install aida --registry https://registry.npmjs.org，仅当前项目可用 - 选项 C "暂不安装" — 只给出手动安装命令，不执行
- 用户选 A：运行
npm install -g aida --registry https://registry.npmjs.org，等待完成 - 用户选 B：运行
npm install aida --registry https://registry.npmjs.org，等待完成 - 用户选 C：输出手动命令后结束
- 用 AskUserQuestion 确认：
-
给出启动命令：输出以下内容后结束，不要替用户运行（避免占用终端）：
npx aida dashboard同时说明：命令运行后会自动打开浏览器，或手动访问终端输出的本地地址。
Notes
- 不要自动运行
aida dashboard，它会占用终端进程，用户应自己在终端里跑 - 安装步骤需要用户授权后才执行，不要默默安装
- 如果安装失败（网络问题等），输出错误信息并建议用户手动运行安装命令
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 · 40 lines · 48 tokens per session scan A b6f74d31bc47
aida-ui is a skill published in the GitHub repository LWTlong/aida (8 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 531 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…