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 Beaulewis1977/claude-plugin-for-codex --skill claude-setupgit clone --depth 1 https://github.com/Beaulewis1977/claude-plugin-for-codexWrote 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/beaulewis1977/claude-plugin-for-codex/claude-setup)<a href="https://agentmods.dev/skills/beaulewis1977/claude-plugin-for-codex/claude-setup"><img src="https://agentmods.dev/badge/skills/beaulewis1977/claude-plugin-for-codex/claude-setup.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.00034 | $0.00296 |
| Opus 5 | $0.00017 | $0.00148 |
| Sonnet 5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
claude-setup 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 8d 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.
What it actually says
Claude Setup
Verify the local bootstrap before asking the shared runtime for a sanitized capability and authentication report.
Workflow
- Check that Node is discoverable using the host-native command:
command -v nodeon POSIX shells orGet-Command nodein PowerShell. Then runnode --version. If Node is absent or the major version is below Node.js 20+, report the actionable prerequisite error and stop because the Node runtime cannot diagnose its own absence. - Resolve
<plugin-root>/scripts/claude-companion.mjsto an absolute path. - Make exactly one runtime invocation. Runtime action:
setup. - Pass
--cwdwith the current workspace and--jsonas separate arguments. Use an argument array; never concatenate or interpolate values into a shell command. - Explain the sanitized result and any repair steps without exposing raw auth output.
The runtime checks the installed CLI, supported flags, version, and
claude auth status. A logged-in Claude.ai subscription is sufficient and
does not require an API key. Anthropic API-key and supported enterprise
provider authentication are also valid. Never print or persist credentials.
What ships with it
1 file 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.
- 8d ago First seen · 30 lines · 34 tokens per session scan A 5b4b729ace37
claude-setup is a skill published in the GitHub repository Beaulewis1977/claude-plugin-for-codex (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 296 once invoked, about $0.0002 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
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…