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-analyzenpx skills add LWTlong/aida --skill aida-analyzegit 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-analyze)<a href="https://agentmods.dev/skills/lwtlong/aida/aida-analyze"><img src="https://agentmods.dev/badge/skills/lwtlong/aida/aida-analyze.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.1 | $0.00042 | $0.00481 |
| Opus 5 | $0.00021 | $0.00241 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
aida-analyze 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 6d 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 Analyze
Goal
Produce a concise, structured analysis of the current feature branch: what changed, the key decisions made, constraints discovered, and what the next developer should know. Then persist it so future sessions can recall it.
Steps
-
Gather context
- Run
git rev-parse --abbrev-ref HEADto confirm the current branch name. - Run
git log $(git merge-base HEAD origin/main)..HEAD --onelineandgit diff $(git merge-base HEAD origin/main)..HEAD --statto scope the changes. Fall back tomain→master→ ask the user iforigin/mainis not found. - Read any relevant source files if the user provides specific paths.
- Run
-
Identify the module — Determine the primary module key (e.g.
auth/login,billing/checkout). Use kebab-case path format matching the source directory structure. -
Extract the key facts:
- What was the requirement or ticket?
- What was the core technical approach?
- What constraints or gotchas were discovered?
- What decisions were made, and why?
- Which files are entry points or hotspots?
-
Call
aida_write_analysiswith the structured data (see Output Format below). -
Report what was saved.
Output Format
After saving, report:
Analysis Saved
Module: <moduleKey>
Ticket: <ticket or "none">
Summary: one sentence describing what this branch does.
Key decisions (up to 5):
- ...
Constraints (up to 3):
- ...
Entry files (up to 5):
- ...
Rules
- If git is unavailable, ask the user to describe what changed.
- Keep summary under 120 chars.
- Decisions should explain WHY, not just WHAT.
- Constraints are non-obvious limits: performance ceilings, data shape assumptions, external API quirks, etc.
- Do NOT invent data — only record facts from the diff or source files.
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.
- 6d ago First seen · 56 lines · 42 tokens per session scan A 5182409acc44
aida-analyze is a skill published in the GitHub repository LWTlong/aida (8 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 481 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…