Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jeet129/praxisnpx agentmods add skills/jeet129/praxis/praxis-startWrote 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/jeet129/praxis/praxis-start)<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-start"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-start/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.
<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-start"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-start.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00440 |
| Opus 5 | $0.00016 | $0.00220 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
praxis-start 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 10d 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
capability: command
domain: codex-plugin
state: active
dependencies: [delivery-planner, architecture-documentation, project-memory]
triggers: [praxis start, bootstrap project, start project, initialize praxis]
outputs: [project_charter, memory_tree, active_gate_summary, next_command]
consumers: [praxis-discover, praxis-audit, praxis-slice]
references: [../../workflows/greenfield-api-service.yaml, ../../workflows/brownfield-enhancement.yaml, ../../governance/governance.yaml]
Praxis Start
Run the Praxis bootstrap flow for Codex.
- Locate the installed plugin root by walking up from this skill until
workflows/andgovernance/are present. - Read
skills/delivery-planner/SKILL.md,skills/project-memory/SKILL.md, andgovernance/governance.yaml. - Create or update
.project/semantic/project-charter.mdwith project mode, data/ML/AI flags, compliance regimes, scale, availability, tenancy, stack, and cloud. - Create the
.project/memory tree if missing. - Summarize active governance gates from
governance/governance.yaml. - Seed per-project governance overrides: copy the plugin's
governance/model-routing.yamlandgovernance/autonomy.yamlto.project/governance/if not already present, then ask the user ONE concise question set — keep default adaptive routing/autonomy, or tuneforce_tier,cost_weights,stop_after,run_budgetfor this engagement. Apply answers to the PROJECT copies only; never edit the plugin's files. - Recommend
$praxis-discoverfor greenfield or$praxis-auditfor brownfield.
Do not modify Claude Code plugin files.
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.
- 10d ago First seen · 32 lines · 33 tokens per session scan A 6fc7ccc98d8d
praxis-start is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 440 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.