factory-record

factory-record is a command for Claude Code from jeet129/praxis. It costs 47 tokens per session (751 once invoked), scanned A, original, MIT.

A command for recording detailed observations about a Praxis artifact, such as a skill, agent, workflow, or command. The record captures what happened, what worked, where the process caused friction, and what should change.

In plain words
What is it for?
Use it after experimenting with a Praxis skill, agent, workflow, or command to document results, edge cases, problems, and suggested refinements.
Why use it?
Automatic logs can show that something ran but not what was learned from using it. This command preserves practical feedback for later review and improvement.

Command for Claude Code

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the praxis plugin — 105 skills, 12 commands, 17 agents, 6 hooks shipped together

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.

agentmods
npx agentmods add commands/jeet129/praxis/factory-record
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.

agentmods badge for factory-record

README.md
[![agentmods](https://agentmods.dev/badge/commands/jeet129/praxis/factory-record.svg)](https://agentmods.dev/commands/jeet129/praxis/factory-record)
Your own site
<a href="https://agentmods.dev/commands/jeet129/praxis/factory-record"><img src="https://agentmods.dev/badge/commands/jeet129/praxis/factory-record.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 751 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00047 $0.00751
Opus 5 $0.00023 $0.00376
Sonnet 5 $0.00009 $0.00150
Haiku 4.5 $0.00005 $0.00075

Measured 4d ago against content hash 233f38fa0eef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 4d 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.

.claude/commands/factory-record.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are recording a factory-metrics observation. This is the rich, human-authored complement to the auto-stub entries that the PostToolUse hook writes — those tell us something happened; this tells us what happened and what we learned.

Step 1 — Identify the artifact

Ask the user (or infer from recent conversation) which artifact they want to record an observation for:

  • Type: skill | agent | workflow | command | hook | gate | reference
  • Name: the artifact's identifier (e.g., requirements-intake, delivery-lead, brownfield-enhancement)

If the user has just been working with a specific praxis artifact in this session, propose it as the default and ask for confirmation.

Step 2 — Capture observation

Ask these in order (skip any the user has already said in this session):

  1. What happened? What was the artifact being used for in this session?
  2. What worked? Where did the discipline land correctly — what did you notice working as designed?
  3. Friction? Where was the artifact clunky, ambiguous, slow, or required workarounds?
  4. Edge cases? Situations the artifact didn't anticipate — what did you have to improvise?
  5. Suggested refinements? What would you change about the artifact based on this use?

Don't insist on all five if the user only has one or two to share. Quality > completeness.

Step 3 — Optional context

If known and the user hasn't said it:

  • Slice id (if in a slice context)
  • Outcome (success / failure / partial)
  • Duration (roughly, in minutes)

Step 4 — Write the file

Compose the markdown body and invoke the recorder script:

# Build observation as a temp file
OBS=$(mktemp)
cat > "$OBS" <<'EOF'
## What worked
{ what the user said about what worked }

## Friction
{ what the user said about friction }

## Edge cases
{ what the user said about edge cases }

## Suggested refinements
{ what the user said about refinements }
EOF

# Call the recorder
"${CLAUDE_PLUGIN_ROOT}/scripts/factory-record.sh" \
    --type        {type} \
    --name        {name} \
    --tool        claude-code \
    --trigger     slash-command \
    --invocation  read \
    --outcome     {outcome or null} \
    --slice       {slice or empty} \
    --duration    {duration in seconds or empty} \
    --observation "$OBS" \
    --mode        per-use

Read the full file on GitHub · 79 lines

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.

  1. 4d ago First seen · 79 lines · 47 tokens per session scan A 233f38fa0eef

Subscribe to this mod's changes

factory-record is a command published in the GitHub repository jeet129/praxis (7 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 751 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.