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-commnpx skills add yacb2/aidex --skill aidex-commgit 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-comm)<a href="https://agentmods.dev/skills/yacb2/aidex/aidex-comm"><img src="https://agentmods.dev/badge/skills/yacb2/aidex/aidex-comm.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.00206 | $0.02574 |
| Opus 5 | $0.00103 | $0.01287 |
| Sonnet 5 | $0.00041 | $0.00515 |
| Haiku 4.5 | $0.00021 | $0.00257 |
Grade A, and why
aidex-comm 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 today.
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 — 216 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-comm"before continuing. Then proceed with the rest of the skill body as normal. If empty/unset, ignore this block.
Communications
Log real correspondence — emails, WhatsApp, calls, meetings — and draft outgoing
messages as consistent .context/communications/ entries. Each entry is a folder
holding a body.md (plus any attachments alongside it). The taxonomy splits on
async vs synchronous: async correspondence has a direction (received/, sent/);
synchronous conversations — meetings and calls — have participants, not a direction, and
live in meetings/. Communications are kept in their native language (D-04
English-default does NOT apply here; D-11 governs skill descriptions, not artifact bodies).
Sub-actions
| Command | Script | Purpose |
|---|---|---|
/aidex-comm new received <slug> [--channel email] |
scripts/new-communication.sh | Scaffold a received async record (email/WhatsApp) under received/ |
/aidex-comm new sent <slug> [--channel whatsapp] |
same | Scaffold an outgoing async draft under sent/ (status starts draft) |
/aidex-comm new meeting <slug> |
same | Scaffold a synchronous meeting record under meetings/ (participant-based, status: sent) |
/aidex-comm new call <slug> |
same | Scaffold a synchronous call record under meetings/ (participant-based, status: sent) |
/aidex-comm migrate |
scripts/migrate-communications.sh | Rename pre-canonical email.md / conversation.md bodies to body.md, reporting each |
--channel is async-only and accepts email (default), whatsapp, other. For meetings
and calls use new meeting / new call — the channel is fixed to the kind.
Dispatch
bash "${CLAUDE_SKILL_DIR}/scripts/new-communication.sh" "$@"
What ships with it
8 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.
- assets/templates/body.md.template 953 B
- assets/templates/meeting.md.template 654 B
- evals/eval-config.json 508 B
- evals/trigger_eval.json 7.1 KB
- scripts/migrate-communications.sh 3.3 KB runs code
- scripts/new-communication.sh 9.5 KB runs code
- tests/test-migrate-communications.sh 4.5 KB runs code
- tests/test-style-profile.sh 4.3 KB runs code
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.
- today Changed · -1 lines 0d83eb627644
- 5d ago First seen · 217 lines · 206 tokens per session scan A f19305c136e3
aidex-comm is a skill published in the GitHub repository yacb2/aidex (2 stars, last pushed yesterday), licensed MIT. It adds 206 tokens to every session and 2,574 once invoked, about $0.0010 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
pdlc-settings
交互式配置 PDLC（当前：状态栏 statusline 的启用/停用/展示项）.
goal-delivery-completeness
Check that delivered work matches the user's goal. Use before final response, release, or handoff.
session-output-contract
Make session output useful, complete, and resumable. Use at handoff, final response, or long-running task summary.
stale-baseline-guard
Avoid acting on outdated context. Use after interruptions, long sessions, branch changes, or concurrent edits.
raycast-automator
Use when the user asks to automate a task with Raycast, build a Raycast extension, create a Raycast script command, or mentions Raycast in the context of building something. Triggers on: "automate X with Raycast", "build a Raycast extension", "create a raycast script", "make a raycast command", or any task where…
weekly
Generate a workplace-facing weekly report from Tracework raw entries, using git only as limited fallback coverage. Supports work, personal, and private all-project scopes. Three modes: quick conversation review ("这周做了啥", "周报简版", "quick weekly", "本周概要"), default Markdown brief ("写周报", "周报", "/tracework:weekly", "weekly…