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-helpnpx skills add LWTlong/aida --skill aida-helpgit 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-help)<a href="https://agentmods.dev/skills/lwtlong/aida/aida-help"><img src="https://agentmods.dev/badge/skills/lwtlong/aida/aida-help.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.00053 | $0.00541 |
| Opus 5 | $0.00026 | $0.00270 |
| Sonnet 5 | $0.00011 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
aida-help 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.
What it actually says
被调用时立即展示下方卡片。只输出这一张表 + 场景提示，不要展开解释。
AIDA 命令
| 命令 | 用途 |
|---|---|
/aida-govern |
一站式治理：扫描 → 分析 → 你确认 → 一次落盘（含 2.x 遗留物清理） |
/aida-audit |
只读扫描，看项目 AI 资产分布和主要问题 |
/aida-remember |
记一条决策为 MADR，Claude Code 后续会自动加载 |
/aida-recall |
召回之前沉淀的模块记忆 |
/aida-analyze |
分支/功能开发完后，让 AI 沉淀"改了什么、为什么" |
/aida-import |
从本地目录路径安全导入外部 Claude Plugin（先审计风险） |
/aida-resolve |
解决 AI 资产文件的 git 合并冲突 |
/aida-sync |
跨工具同步规则：Claude ↔ Cursor ↔ Codex（你选源→目标） |
/aida-pkg |
打包资产为 Claude Plugin 分享 |
/aida-undo |
回滚最近一次 AIDA 写操作 |
/aida-remember-branch |
从当前分支的 diff 批量提取决策 |
/aida-ui |
打开 AIDA Dashboard 本地 UI（检查安装 → 给出启动命令） |
/aida-help |
显示这张卡片 |
常见场景
- 刚接手项目 →
/aida-audit - 规则乱了 →
/aida-govern - 治理搞砸了 →
/aida-undo - 想沉淀"为什么这么写" →
/aida-remember - 分支写完想批量沉淀 →
/aida-remember-branch - 接手老模块前 →
/aida-recall - 分享给团队 →
/aida-pkg - 想看资产可视化 →
/aida-ui
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 · 36 lines · 53 tokens per session scan A 7de49bdecf78
aida-help is a skill published in the GitHub repository LWTlong/aida (8 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 541 once invoked, about $0.0003 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…