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-factory-recordgit 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-factory-record)<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-factory-record"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-factory-record/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-factory-record"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-factory-record.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.00056 | $0.00455 |
| Opus 5 | $0.00028 | $0.00228 |
| Sonnet 5 | $0.00011 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
praxis-factory-record 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: [factory-evaluation]
triggers: [praxis factory record, record observation, capture what we learned, log for steward]
outputs: [factory_metrics_observation]
consumers: [praxis-steward]
references: [../../references/factory-metrics-schema.md]
Praxis Factory Record
Record a rich factory-metrics observation — a human judgment about how a skill, agent, workflow, or command performed — for the System Steward's quarterly review.
Steps
- Ask the user (once, concisely) for anything not already clear from context: which artifact (skill/agent/workflow/command slug), what happened, and the verdict flavor (worked well | over-engineered | misfired | gap).
- Run the recorder script from the installed plugin root:
(locate the plugin root by walking up from this skill untilbash <plugin-root>/scripts/factory-record.shscripts/is present). If the script prompts interactively, relay its prompts; if invoked with arguments, pass the observation through. - Confirm the observation landed under
.project/operational/factory-metrics/with the structured frontmatter per../../references/factory-metrics-schema.md— an observation without the frontmatter is incomplete.
What you must not do
- Do NOT paraphrase the user's judgment into blandness — record their actual verdict, including negative ones; the steward needs honest signal.
- Do NOT skip the structured frontmatter (slug, verdict, date) — free prose alone is unusable by
factory-usage-report.py.
Reference
Schema: ../../references/factory-metrics-schema.md. Consumed at $praxis-steward (quarterly review).
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 · 41 lines · 56 tokens per session scan A 1ba25f812e8e
praxis-factory-record is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 455 once invoked, about $0.0003 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…