What is praxis-setup-subagents?

A setup command that installs role-specific Codex subagent profiles into a repository. Subagents are agents configured for particular development roles.

Use it when installing or updating the Praxis subagents in a repository so workflows such as slicing, reviewing, and architecture work can use those profiles.

It gives Codex the project-specific agent profiles needed to delegate work consistently, while applying the project's model settings.

praxis-setup-subagents — Skill for Claude Code by jeet129

Install

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.

Any agent

npx skills add jeet129/praxis --skill praxis-setup-subagents

Clone the repo

git clone --depth 1 https://github.com/jeet129/praxis

Made for: Claude Code.

Or install praxis, the plugin that ships this one along with the rest of its 105 skills, 12 commands, 17 agents, 6 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jeet129/praxis/praxis-setup-subagents/github.svg)](https://agentmods.dev/skills/jeet129/praxis/praxis-setup-subagents)

Your own site

<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-setup-subagents"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-setup-subagents/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-setup-subagents"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-setup-subagents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 537 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00029	$0.00537
Opus 5	$0.00015	$0.00269
Sonnet 5	$0.00006	$0.00107
Haiku 4.5	$0.00003	$0.00054

Measured 9d ago against content hash 9bcccbc6d5c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

praxis-setup-subagents 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 9d 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.

codex-plugin-assets/skills/praxis-setup-subagents/SKILL.md · 38 lines

What it actually says

capability: command
domain: codex-plugin
state: active
dependencies: []
triggers: [praxis setup subagents, install subagents, codex agents, setup codex agents]
outputs: [codex_agent_profiles]
consumers: [praxis-slice, praxis-review, praxis-architect]
references: [../../codex-agents]

Praxis Setup Subagents

Install Praxis Codex subagent profiles into the current repository.

Locate the installed plugin root by walking up from this skill until codex-agents/ is present (call it PLUGIN_ROOT). The target repo is the current working directory (TARGET).
Create .codex/agents/ in the target repository if missing.
Copy codex-agents/*.toml into TARGET/.codex/agents/. On a fresh install, don't overwrite existing files unless the user approves. On a refresh/update, DO overwrite — old copies carry stale model / model_reasoning_effort values.
Apply this project's model routing to the installed profiles so a project-level override takes effect (the whole point of an override — you never hardcode models in the plugin defaults):
```
python3 "$PLUGIN_ROOT/scripts/apply-model-routing.py" --project-dir "$TARGET" --codex-out "$TARGET/.codex/agents"
```
This resolves each agent's tier → model + model_reasoning_effort from TARGET/.project/governance/model-routing.yaml when it exists (project override wins), else the plugin default. With the default (model_map: auto), no model line is written and each subagent inherits the Codex session's model; set concrete model IDs in the project override's model_map to pin them. It rewrites only the routing lines in TARGET/.codex/agents/*.toml and never touches the plugin's own files.
Tell the user to restart Codex or start a new session so the profiles are loaded.

These files are Codex-specific. They do not affect Claude Code.

Re-run this skill (steps 3-4, overwriting) whenever the plugin updates OR you change .project/governance/model-routing.yaml — that is how routing changes reach the subagent profiles.

Changes

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.

9d ago First seen · 38 lines · 29 tokens per session scan A 9bcccbc6d5c6

Subscribe to this mod's changes

praxis-setup-subagents is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 537 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-31.

Building agents

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens