agentmods.dev

process

process is a command for Claude Code from stellarshenson/claude-code-plugins. It costs 19 tokens per session (379 once invoked), scanned A, original, MIT.

A workflow for turning input documents into a structured, checked deliverable. It moves through analysis, drafting, source checking, formatting, and final delivery.

In plain words
What is it for?
Use it to create reports or other documents from files in an input folder, verify claims against references, standardize the result, and save the final output.
Why use it?
It organizes the work and leaves intermediate files and checks in a working area, reducing the chance that important source material or verification steps are missed.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Part of the document-processing plugin — 5 skills, 5 commands shipped together

not rated 4repo changed 21d ago A scan 19 tokens original MIT

Good fit Use it to create reports or other documents from files in an input folder, verify claims against references, standardize the result, and save the final output.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/stellarshenson/claude-code-plugins/process
View source ↗ stellarshenson/claude-code-plugins
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.

Clone the repo
git clone --depth 1 https://github.com/stellarshenson/claude-code-plugins

Made for: Claude Code.

Or install document-processing, the plugin that ships this one along with the rest of its 5 skills, 5 commands.

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 process

README.md
[![agentmods](https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/process/github.svg)](https://agentmods.dev/commands/stellarshenson/claude-code-plugins/process)
Your own site
<a href="https://agentmods.dev/commands/stellarshenson/claude-code-plugins/process"><img src="https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/process/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.

agentmods 80×15 button for process

Your own site · 80×15
<a href="https://agentmods.dev/commands/stellarshenson/claude-code-plugins/process"><img src="https://agentmods.dev/badge/commands/stellarshenson/claude-code-plugins/process.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 379 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00019 $0.00379
Opus 5.5 $0.00008 $0.00152
Sonnet 5.5 $0.00004 $0.00076
Haiku 4.5 $0.00002 $0.00038

Measured 21d ago against content hash 0adf5e9837a8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

process 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 21d 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.

plugins/document-processing/commands/process.md · 38 lines

What it actually says

Document Processing - Process

Read this plugin's skill file skills/process/SKILL.md and follow it with the user objective. Skill refines objective, generates INSTRUCTIONS.md + BENCHMARK.md (each for user approval), scaffolds WIP folder, then runs four-phase workflow.

Flow

  1. Read this plugin's skill file skills/process/SKILL.md and follow it with the user objective
  2. Skill handles: objective refinement -> program generation -> benchmark generation -> scaffolding -> execution (Analyze & Draft -> Verify & Ground -> Uniformize & Deliver)
  3. Verify & Ground phase invokes grounding skill for CLI-assisted claim grounding
  4. All intermediate work -> 2-wip/<task-name>/
  5. Final output -> 3-output/

Prerequisites

  • 1-input/ directory with source documents
  • Optionally 4-references/ with examples and facts

When NOT to use this

  • Validating finished document against its source -> use /document-processing:validate
  • Bare claim grounding (single claim or batch) -> use /document-processing:grounding
  • Updating existing 3-output/ document -> use /document-processing:update

Examples

/document-processing:process reconstruct complete timeline from all court documents
/document-processing:process draft response addressing mother's claims using evidence from hearings
/document-processing:process extract and categorize all findings by topic with source citations
/document-processing:process synthesize expert opinions into unified position paper
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. 21d ago Changed 0adf5e9837a8
  2. 1mo ago First seen · 38 lines · 19 tokens per session scan A 06272ceaccfb

Subscribe to this mod's changes

process is a command published in the GitHub repository stellarshenson/claude-code-plugins (4 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 379 once invoked, about $0.0001 per session on Opus 5.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.

DocumentsWriting and docs
Related

Other commands, from other repositories

brand-generate

Generate an on-brand document from a saved Brand Profile.

ferdinandobons/brand-docs · 0 tokens

render-figures

Compile all .tex and .typ figure files in a directory.

braininahat/brains-in-a-hat · 17 tokens

cti-report

Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].

7onez/cti-expert · 45 tokens

ppt-image2-editable-rebuild

Rebuild image2 or imagegen reference slides as editable PowerPoint decks.

wwe-dog/ppt-image2-editable-rebuild · 15 tokens

harness-onboarding

Generate a human-readable onboarding document from HARNESS.md, AGENTS.md, and REFLECTIONLOG.md — a friendly guide for new team members.

Habitat-Thinking/ai-literacy-superpowers · 33 tokens

publish-api-docs

Generate interactive API documentation from blueprint specs (Swagger UI, Redoc, AsyncAPI).

navraj007in/architecture-cowork-plugin · 17 tokens