agentmods.dev

process-control

process-control is a skill for Claude Code from ChrisGVE/localdata-mcp. It costs 28 tokens per session (586 once invoked), scanned A, original, Apache-2.0.

A statistical process-control tool for checking whether a measured process stays stable over time and whether it can meet quality targets.

In plain words
What is it for?
Use it to build control charts, calculate process capability, and report unusual patterns such as points outside control limits or long runs on one side of the average.
Why use it?
It helps separate normal variation from signs that a process has changed or gone out of control.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the localdata-mcp plugin — 18 skills, 11 agents, 1 MCP server shipped together

not rated 4repo +1 24d ago A scan 28 tokens original Apache-2.0

Good fit Use it to build control charts, calculate process capability, and report unusual patterns such as points outside control limits or long runs on one side of the average.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chrisgve/localdata-mcp/process-control
View source ↗ ChrisGVE/localdata-mcp
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.

Any agent
npx skills add ChrisGVE/localdata-mcp --skill process-control
Clone the repo
git clone --depth 1 https://github.com/ChrisGVE/localdata-mcp

Made for: Claude Code.

Or install localdata-mcp, the plugin that ships this one along with the rest of its 18 skills, 11 agents, 1 MCP server.

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-control

README.md
[![agentmods](https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/process-control.svg)](https://agentmods.dev/skills/chrisgve/localdata-mcp/process-control)
Your own site
<a href="https://agentmods.dev/skills/chrisgve/localdata-mcp/process-control"><img src="https://agentmods.dev/badge/skills/chrisgve/localdata-mcp/process-control.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 586 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.00028 $0.00586
Opus 5 $0.00014 $0.00293
Sonnet 5 $0.00006 $0.00117
Haiku 4.5 $0.00003 $0.00059

Measured 8d ago against content hash 7de7342b6208, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

process-control 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 8d 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.

skills/workflow/process-control/SKILL.md · 47 lines

How it starts

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

Process Control

Assess process stability using statistical process control methods and determine process capability.

Steps

  1. Parse arguments. Extract the database name and measurement column from $ARGUMENTS. The measurement column is the quality characteristic being monitored.

  2. Extract process data. Call describe_database to understand the data structure. Call execute_query to pull the measurement column along with any timestamp, batch, or subgroup identifier. Sort by time order.

  3. Compute control chart statistics. Call execute_query to calculate:

    • Overall mean (center line)
    • Within-subgroup variation (R-bar or S-bar) for control limits
    • Upper and lower control limits (mean +/- 3 sigma)
    • Subgroup means and ranges if subgroups exist

  4. Test for stability. Examine the data against Western Electric rules:

    • Points beyond control limits
    • 7+ consecutive points on one side of the center line (run)
    • 6+ consecutive points trending in one direction
    • 2 of 3 consecutive points beyond 2-sigma Report any violations with their location in the time series.

  5. Detect anomalies. Call detect_anomalies on the measurement series as a complementary check. Compare algorithm-detected anomalies with control chart violations.

  6. Assess process capability. If specification limits are available:

    • Calculate Cp (potential capability): specification width / process width
    • Calculate Cpk (actual capability): minimum distance to spec limit / half process width
    • Estimate percentage out of specification
    • Cp >= 1.33 and Cpk >= 1.0 are typical minimums

  7. Test for shifts. If the process appears unstable, call analyze_hypothesis_test to compare measurements before and after suspected change points. Call analyze_effect_sizes to quantify the magnitude of any shift.

  8. Present results. Provide:

    • Control chart summary: center line, control limits, violations found
    • Stability assessment: in control or out of control, with evidence
    • Capability indices (Cp, Cpk) if specifications were provided
    • Identified assignable causes or patterns
    • Recommendations: investigate specific violations, adjust process, or continue monitoring

Read the full file on GitHub · 47 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. 8d ago First seen · 47 lines · 28 tokens per session scan A 7de7342b6208

Subscribe to this mod's changes

process-control is a skill published in the GitHub repository ChrisGVE/localdata-mcp (4 stars, last pushed 24d ago), licensed Apache-2.0. It adds 28 tokens to every session and 586 once invoked, about $0.0001 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.

Analytics and metricsClaude Codeai-toolsclaude-desktopdata-analyticsfastmcpmcp
Related

Other skills, from other repositories

wingman-mcp

Add persistent, interactive task plan management to your agent. Wingman tracks plans and tasks across a long conversation — Claude creates plans, ticks tasks after completing work, and a live panel renders inline in the chat. Install the MCP server first, then use these tools to manage plans and tasks throughout any…

adeoluwaadesina/wingman-mcp · 68 tokens

liveagent-code-review

Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.

Stack-Cairn/LiveAgent · 54 tokens

skills-creator

Create or update LiveAgent runtime skills. Use when you need to summarize a workflow into a skill, write it into the fixed user skills root, validate it, package it, or refine a skill's references for LiveAgent's SkillsManager flow.

Stack-Cairn/LiveAgent · 53 tokens

skills-installer

Install, list enabled, validate, or package LiveAgent skills. Use when you need to inspect the skills enabled in the current conversation, import a local skill directory or package, search/install from ClawHub, install from a GitHub repo/tree URL, or reconcile conflicts during an upgrade.

Stack-Cairn/LiveAgent · 62 tokens

triaging-incidents

Creating, triaging, updating, and analyzing ServiceNow incidents. Assess severity, check affected CIs, find related incidents, and recommend assignments. Use when the user mentions incidents, INC numbers, outages, service disruptions, ticket creation, triage, priority, severity, ITSM operations, SLA breaches…

jschuller/mcp-server-servicenow · 82 tokens

reviewing-update-sets

Reviewing, analyzing, and comparing ServiceNow update sets before promotion. Shows changes, risks, dependencies, and conflicts. Use when the user mentions update sets, customizations, promotion, code review, change tracking, pre-deployment review, sysupdatexml, customer updates, "what changed in this update set," or…

jschuller/mcp-server-servicenow · 77 tokens