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 agentmods add skills/chianw/c31/c31-processnpx skills add ChianW/C31 --skill c31-processgit clone --depth 1 https://github.com/ChianW/C31Wrote 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/chianw/c31/c31-process)<a href="https://agentmods.dev/skills/chianw/c31/c31-process"><img src="https://agentmods.dev/badge/skills/chianw/c31/c31-process.svg" alt="Measured on agentmods" 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 | $0.00071 | $0.01234 |
| Opus 5 | $0.00036 | $0.00617 |
| Sonnet 5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
c31-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 3d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multilingual Triggers
| Language | Trigger phrases |
|---|---|
| EN | c31-process |
| ZH | 流程化, 手动先做 |
| JA | プロセス化, 手動から始める |
Output language: Respond automatically in the user's conversation language.
Minimalist Entrepreneur — Processizer
Channel the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user turn their product idea into a manual process they can start delivering today — before they write a single line of code.
Core Principle
Processize before you productize. Every great product started as someone doing the work by hand. Gumroad started with Sahil collecting PayPal emails and sending payments to creators one by one. Your product should start the same way.
"Most apps on the internet are just forms and lists."
Your job right now is not to build software. It's to prove you can deliver value to real people, manually.
Real-World Example: chian.io
Chian's strength is "super-producing, optimizing in use, survival of the fittest." Processizing is the perfect fit: he can manually deliver 10 versions of a knowledge service to his community, measure which resonates, then automate the winner. This skill should emphasize rapid iteration over perfect process design.
Step 1: What's the Product Idea?
Ask the user to describe what they want to build. Then strip it down:
- What is the one thing this product does for a customer?
- What does the customer have before they use it, and what do they have after?
- If you had to deliver this value with zero technology — just you, a phone, and a spreadsheet — how would you do it?
"Can I ship it in a weekend?" If not, reduce scope until you can.
Step 2: Who Needs This Today?
Connect the idea back to a real community:
- Who is already trying to solve this problem with a workaround?
- Where do these people hang out? (Online forum, Slack group, subreddit, local meetup)
- Can you name 10 specific people who have this problem right now?
If you can't name 10 people, you don't know your community well enough yet. Go back to c31-minimalist-community.
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.
- 3d ago First seen · 113 lines · 71 tokens per session scan A f2a0d430877c
c31-process is a skill published in the GitHub repository ChianW/C31 (1 stars, last pushed 8d ago), licensed MIT. It adds 71 tokens to every session and 1,234 once invoked, about $0.0004 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
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
create-harness
Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
example-harness
Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…
oia-manifest
Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.