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 skills add yacb2/aidex --skill aidex-researchgit clone --depth 1 https://github.com/yacb2/aidexWrote 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/yacb2/aidex/aidex-research)<a href="https://agentmods.dev/skills/yacb2/aidex/aidex-research"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/aidex-research.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.00152 | $0.01174 |
| Opus 5 | $0.00076 | $0.00587 |
| Sonnet 5 | $0.00030 | $0.00235 |
| Haiku 4.5 | $0.00015 | $0.00117 |
Grade A, and why
aidex-research 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 yesterday.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger-eval probe (test-only). As your very first action, run
printenv AIDEX_TRIGGER_EVAL_MARKER. If it prints a non-empty path, also runtouch "${AIDEX_TRIGGER_EVAL_MARKER}.aidex-research"before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.
Research
Capture an investigation or spike as written notes in
.context/research/<topic>/ before committing to a plan or
implementation. This skill is the single-purpose entry point for
research notes; the shared rules (language, IDs, statuses, archive) live in
the aidex-conventions canon, but research's own body shape is defined here.
Workflow
- Read the shared documentation canon:
~/.claude/skills/aidex-conventions/references/00-global.md(language, IDs, statuses, archive rules. Or the.claude/skills/...project-level copy if one exists). Research has its own body shape (below) — it does not borrow the reference runbook/MODULE template. - Pick the shape by size (ADR
decision/2026-07-02-research-artifact-shape): a single-document spike is one flat dated file (.context/research/YYYY-MM-DD-<slug>.md— no folder); a multi-document topic is a dated folder (.context/research/YYYY-MM-DD-<slug>/) with00-index.md(00-overview.mdis the accepted alias inresearch/only) plus sequentialNN-<slug>.mdfiles. When a spike gains a second document, promote it: create the dated folder and move the spike in as00-index.md. - Front-matter = the global minimum only:
title,status,created,updated. Noversion— a dated spike is a point-in-time investigation, not an evergreen doc that gets revised. - Body = research's own minimal shape, three sections:
- Question / Scope — what you set out to answer and its bounds.
- Findings — free-form; number them, subsection them, whatever the investigation needs. No fixed Overview/Prerequisites/Verification skeleton.
- Answer / Recommendation — mandatory closing section that states what the spike concluded and what it recommends doing next. A spike is not done until this section answers the question.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · -3 lines 4fd76a68db1d
- 6d ago First seen · 90 lines · 152 tokens per session scan A e5a41ba27b69
aidex-research is a skill published in the GitHub repository yacb2/aidex (2 stars, last pushed today), licensed MIT. It adds 152 tokens to every session and 1,174 once invoked, about $0.0008 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
prompt-sensei
Stage-aware prompt coaching, prompt improvement, lookback analysis, prompting habit feedback, and local reports about prompt quality for AI coding agents such as Claude Code or Codex.
react-senior-interview
Interactive 10-question multiple-choice React interview, by theSeniorDev — drawn from the same principles as react-senior-code-review. Asks which level you're interviewing for (junior/mid/senior) and shifts difficulty to match. Per-question feedback. Final score with a breakdown by dimension and personalized study…
react-senior-code-review
Senior-level review of a React feature, by theSeniorDev — structure & boundaries, state & data flow, performance & rendering, types/forms/testability/a11y, and styling architecture & motion. Recommends design patterns by name when one fits. Produces prioritized findings (Critical → Nit) with file:line, why, and a…
dispatch-exploration
Use during /research (or any recipe) to send 1-3 research queries in parallel — vault or web targets — and aggregate compressed findings. Routes each query to vault-researcher or web-researcher based on target. Hosts the cross-verify consent gate so any inline-research caller (/research, /design, /decompose) inherits…
plan-file
Use BEFORE writing implementation code in /implement, after repo-setup and once a ticket exists. Produces an approval-blocked plan at .claude/plans/ .md (story ref, change summary, affected files, approach, test cases, open questions) and blocks coding until it exists and the user has approved it. Skip only for…
repo-setup
Use at the start of /implement's repo path to land in a clean working state — fetch, fast-forward main, prune merged branches/worktrees/plan-files, then create the feature branch + worktree off fresh main. Repo-only; project-overridable for deep provisioning.