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/ai-analyst-lab/ai-analyst-plugin/analysis-designnpx skills add ai-analyst-lab/ai-analyst-plugin --skill analysis-designgit clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-pluginWrote 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/ai-analyst-lab/ai-analyst-plugin/analysis-design)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst-plugin/analysis-design"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst-plugin/analysis-design.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.00109 | $0.03149 |
| Opus 5 | $0.00055 | $0.01574 |
| Sonnet 5 | $0.00022 | $0.00630 |
| Haiku 4.5 | $0.00011 | $0.00315 |
Grade A, and why
analysis-design 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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Analysis Design
Trigger: /analysis-design, "design an analysis for...", "I think X caused Y", "help me investigate..."
Type: Orchestrator — runs a multi-agent pipeline
Purpose
Takes a vague analytical hunch, stakeholder request, or business question and produces a rigorous, stakeholder-ready analysis plan through a multi-stage pipeline. Chains three specialized agents: Hypothesis Sharpener → Confound Scanner → (optional) Feedback Synthesizer.
This skill orchestrates the full lifecycle: hunch → testable hypothesis → threat assessment → investigation plan → V1 execution → feedback synthesis → V2 redesign.
When to Use
- A PM has a hunch but no plan: "I think removing the widget caused repeat purchases to drop"
- A vague request lands: "Can you look into why conversion dropped?"
- An analysis needs redesign after stakeholder feedback: "Here's V1 and the comments — help me build V2"
- Before starting any major investigation (prevents wasted work)
Inputs
| Input | Required | Source | Description |
|---|---|---|---|
{{HUNCH}} |
Yes | User | The vague hypothesis, business question, or analytical request |
{{DATA_PATH}} |
No | User or auto-detect | Path to relevant dataset(s). If not provided, uses active dataset from .knowledge/active.yaml |
{{AUDIENCE}} |
No | User | Who will consume the analysis (e.g., "VP of Product", "exec team", "cross-functional leads") |
{{V1_FINDINGS}} |
No | User or working/ | Path to V1 analysis output — triggers V2 redesign flow |
{{FEEDBACK}} |
No | User | Stakeholder feedback (comments, meeting transcript, Slack thread) — triggers Feedback Synthesizer |
{{URGENCY}} |
No | User | Timeline constraint (e.g., "need by EOD", "board meeting Friday"). Affects investigation depth. |
CRITICAL: First Action - Show Architecture Preview
BEFORE doing ANYTHING else, output the architecture preview. This is the very first thing you do when this skill is invoked. Do not read agent files, do not start Stage 1, do not process inputs — show the preview first.
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 · 318 lines · 109 tokens per session scan A 48e8da679bf0
analysis-design is a skill published in the GitHub repository ai-analyst-lab/ai-analyst-plugin (32 stars, last pushed 9d ago), licensed MIT. It adds 109 tokens to every session and 3,149 once invoked, about $0.0005 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 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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…