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-intakeWrote 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-intake)<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-intake"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-intake/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-intake"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-intake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 37 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00093 | $0.00730 |
| Opus 5 | $0.00046 | $0.00365 |
| Sonnet 5 | $0.00019 | $0.00146 |
| Haiku 4.5 | $0.00009 | $0.00073 |
Grade A, and why
praxis-intake 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
capability: command
domain: codex-plugin
state: active
dependencies: [requirements-intake, impact-analysis, adaptive-model-routing]
triggers: [praxis intake, new requirement, new story, new epic, intake this, we have a ticket, new change request]
outputs: [inbox_entry, triage_decision, routed_work]
consumers: [praxis-slice, praxis-discover, praxis-architect, praxis-drive]
references: [../../skills/requirements-intake, ../../skills/impact-analysis]
Praxis Intake
The ONE command to run when a new requirement arrives after the initial discovery + architecture rounds are complete — a story, epic, ticket, stakeholder ask, bug-disguised-as-feature, or change request. Do NOT decide the workflow yourself and do NOT jump straight to coding; run the requirements-intake discipline (../../skills/requirements-intake) and let it right-size the ask.
Steps
- Capture. Append the incoming ask to
.project/working/inbox.md(append-only queue). - Triage. Decide size (one slice | several slices | needs architecture), blast radius (which modules
impact-analysismust cover), and owner. Record in.project/working/inbox-decisions.md. - Right-size and route — pick the LIGHTEST safe path:
- Small, well-understood, low blast radius, clear AC → have
delivery-lead→lead-developerproduce a slice ledger and hand to drive ($praxis-drive). No full ceremony. - Touches load-bearing / existing behavior → run
impact-analysisFIRST, then slice. - Large or cross-cutting (new subsystem, schema change, new NFR) → group with related items into a mini intake brief →
$praxis-discover→$praxis-architect(gated) →project-phasing→ slices. - Feasibility genuinely unknown → spike.
- P0/P1 production break → expedited-change.
- Small, well-understood, low blast radius, clear AC → have
- Report and proceed. State the routing decision + WHY in one or two lines, then proceed — stopping only at the one human gate the chosen route requires (architecture_sign_off, spike_disposition, production_go_live, etc.).
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 · 45 lines · 93 tokens per session scan A 5c87cc79faa8
praxis-intake is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 6d ago), licensed MIT. It adds 93 tokens to every session and 730 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.