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/yacb2/aidex/aidex-requestnpx skills add yacb2/aidex --skill aidex-requestgit 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-request)<a href="https://agentmods.dev/skills/yacb2/aidex/aidex-request"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/aidex-request.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.00160 | $0.00935 |
| Opus 5 | $0.00080 | $0.00467 |
| Sonnet 5 | $0.00032 | $0.00187 |
| Haiku 4.5 | $0.00016 | $0.00093 |
Grade A, and why
aidex-request 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.
How it starts
The opening of the file, as written. The whole thing — 74 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-request"before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.
Request
Capture an incoming stakeholder, client, or product request as a written
item in .context/requests/ before anyone acts on it. This skill is the
single-purpose entry point for request capture; the formatting canon
lives in the shared aidex-conventions reference package (not forked here).
Workflow
- Read the request conventions canon:
~/.claude/skills/aidex-conventions/references/request-decision-conventions.md(Requests section; or.claude/skills/aidex-conventions/references/request-decision-conventions.mdif a project-level copy exists). - Create a single dated file:
.context/requests/YYYY-MM-DD-<slug>.md(slug kebab-case, dateYYYY-MM-DD). - Front-matter per the canon — base lifecycle status
(
open/doing/done/dropped) plusorigin,origin_ref,priority,escalated_to,blocked_by. - Body per the canon template: Description, Context, Acceptance Criteria, Outcome. A request is always a single file; if it needs depth it escalates to a plan or research. Write the artifact in English (canon §Language).
Closing a request
When a request reaches a terminal state, close it atomically (stamps updated,
sets the terminal status, archives per D-10) instead of hand-editing:
bash ~/.claude/skills/aidex-conventions/scripts/close-dated-artifact.sh requests <slug> [--status done|dropped]
A request escalated to a plan sets escalated_to: plan/<slug> first, then closes
with --status done.
Self-check (mandatory close step)
Before finishing, validate the artifact you just wrote and fix any violation on the spot — compliance is enforced at creation time, not left to a later sweep:
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.
- 4d ago First seen · 74 lines · 160 tokens per session scan A 135774083ace
aidex-request is a skill published in the GitHub repository yacb2/aidex (2 stars, last pushed 6d ago), licensed MIT. It adds 160 tokens to every session and 935 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
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
orchestrate
Pipeline orchestration: dispatch the highest-priority ready tasks/work units to agents, manage capacity, and coordinate the Todo to Done flow. Invoked as /agiflow:orchestrate. Uses listtasks, listactivetasksbyorg, listmembers, updatetask, getworkunitprogress.