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/ndycode/codex-multi-auth/examplenpx skills add ndycode/codex-multi-auth --skill examplegit clone --depth 1 https://github.com/ndycode/codex-multi-authWhat 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.00010 | $0.00031 |
| Opus 5 | $0.00005 | $0.00015 |
| Sonnet 5 | $0.00002 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
example 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.
What it actually says
Example
This fixture skill exists to satisfy the plugin scanner regression test.
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 First seen · 9 lines · 10 tokens per session scan A 33e3de92b4a0
example is a skill published in the GitHub repository ndycode/codex-multi-auth (465 stars, last pushed yesterday), licensed MIT. It adds 10 tokens to every session and 31 once invoked, about $0.0001 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
codexu-release
Run this skill from the repository root. Treat the release as a real public publish: verify the current remote state first, keep unrelated user changes out of release commits, and report exactly what was built, pushed, and released.
codexu-pr-review
Review codexU pull requests and decide whether they should be merged, changed, split, declined, or kept as a fork based on product positioning, roadmap, privacy, data semantics, native macOS design, architecture, scope, and verification. Use for PR review, mergeability assessment, contribution triage, and feature-fit…
npm-security-best-practices
Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.
rembric-dashboard-ui
Brutalist Rembric dashboard UI work — building / editing / extending pages, styles, components, modals, tables, filters, pagination, mobile responsive, destructive confirmations. Use when the user asks for changes under src/dashboard/, mentions Rembric design tokens (lime, brutalist, sidebar, view-head, hl-lime), or…
review-and-ship
Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.
codex-hud
Show Codex workspace context with local config, git state, hooks, and project hints. Standalone mode can show an expanded snapshot; patched Codex TUI footer mode is single-line. Use when the user says "codex-hud", "show Codex HUD", "status HUD", "workspace snapshot", or asks for richer Codex context.