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-pkgnpx skills add LWTlong/aida --skill aida-pkggit 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-pkg)<a href="https://agentmods.dev/skills/lwtlong/aida/aida-pkg"><img src="https://agentmods.dev/badge/skills/lwtlong/aida/aida-pkg.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.00060 | $0.00511 |
| Opus 5 | $0.00030 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
aida-pkg 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 3d 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 Package
Goal
Package the right assets into a shareable Claude Plugin with minimal noise and clear risk. Also supports packaging the built-in AIDA skills themselves.
Two Modes
Mode A: Package Project Assets
Package rules, skills, docs, etc. from the current project for team sharing.
- Call
aida_list_assetsto enumerate available assets. - Select the safest and most reusable assets (rules with IDs, skill files with clear descriptions).
- Confirm the selection with the user.
- Call
aida_build_pluginwith the selectedassetIds, aname,description, and optionalversion. - Call
aida_audit_plugin_riskon the returnedoutputPath. - Show the risk report and advise on next steps.
Mode B: Package AIDA Itself
Package all built-in AIDA skills (aida-govern, aida-audit, aida-remember, etc.) as a self-contained plugin for team sharing.
- Call
aida_build_self_plugin(no args needed — outputs to.aida/plugins/aida-<version>/by default). - Show the returned
outputPathandskillslist. - Tell the user: share the output directory with teammates who can install it via their AI tool's plugin install flow, or
aida copy-to cursorto copy skills to.cursor/.
Safety Rules
- Always run
aida_audit_plugin_riskon Mode A output before sharing. - Do not include tokens, private URLs, or absolute local paths in packaged assets.
- If risk level is
high, show full findings and let the user decide before sharing.
Output Format
Result
| Metric | Value |
|---|---|
| Mode | A — project assets / B — AIDA self |
| Assets / Skills included | N |
| Output path | .aida/plugins/... |
| Risk level | low / medium / high |
Next steps: Share the output directory with teammates, or install into .claude/ via your AI tool's plugin flow.
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.
- 3d ago First seen · 46 lines · 60 tokens per session scan A c47ad8fd6906
aida-pkg is a skill published in the GitHub repository LWTlong/aida (8 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 511 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…