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 jeet129/praxis --skill praxis-refine-ideagit clone --depth 1 https://github.com/jeet129/praxisWrote 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-refine-idea)<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-refine-idea"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-refine-idea/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-refine-idea"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-refine-idea.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.00049 | $0.00434 |
| Opus 5 | $0.00024 | $0.00217 |
| Sonnet 5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
praxis-refine-idea 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 11d 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: [agentic-harness-orchestration, requirements-interrogation, doubt-driven-decisions]
triggers: [praxis refine idea, refine idea, refine this concept, iterate on this proposal, ideation refinement]
outputs: [refined_artifact, refinement_log, convergence_summary, role_binding_record]
consumers: [praxis-discover, praxis-start]
references: [../../workflows/ideation-refinement-loop.yaml]
Praxis Refine Idea
Run the ideation-refinement-loop workflow against an ideation artifact.
- Resolve the artifact or topic from the user prompt; confirm harness bindings for creator, reviewer, enhancer, and arbiter roles (defaults per the workflow's
runtime_bindings). - Initialize the run: record role bindings and create the refinement log so the run is reproducible.
- Creator pass produces the draft (or ingests the supplied artifact) with assumptions and open questions.
- Loop, bounded by
max_passes: reviewer produces severity-tagged findings against the review lenses; enhancer revises with a change log and rejected-feedback rationale; arbiter scores convergence against the pre-enhancer version. - Exit the loop when no findings at or above major remain and the next pass's expected value is cosmetic/low — or when
max_passesis exhausted. - Present the convergence summary and remaining risks to the user; the
ideation_refinement_approvalgate requires their explicit approval or a request for another pass. - Record the final artifact path and refinement log under
.project/working/.
Do not silently accept the enhancer's revision — every pass is scored by the arbiter before it becomes the current artifact.
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.
- 11d ago First seen · 32 lines · 49 tokens per session scan A ab95baeb16ba
praxis-refine-idea is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 434 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…