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 chenchihcu/DevSpace-MCP --skill process-stat-chartgit clone --depth 1 https://github.com/chenchihcu/DevSpace-MCPWrote 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/chenchihcu/devspace-mcp/process-stat-chart)<a href="https://agentmods.dev/skills/chenchihcu/devspace-mcp/process-stat-chart"><img src="https://agentmods.dev/badge/skills/chenchihcu/devspace-mcp/process-stat-chart/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/chenchihcu/devspace-mcp/process-stat-chart"><img src="https://agentmods.dev/badge/skills/chenchihcu/devspace-mcp/process-stat-chart.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.00025 | $0.00312 |
| Opus 5.5 | $0.00010 | $0.00125 |
| Sonnet 5.5 | $0.00005 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
process-stat-chart 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 1mo 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
process-stat-chart
Purpose
Specify process statistics charts and reports while preserving statistical meaning and chart-to-data traceability.
When to Use
- SPC, SPI, Cp/Cpk, control chart, or process abnormality reporting.
- Planning chart specs before creating artifacts.
- Reviewing whether chart conclusions are supported by data.
Inputs
- Raw process measurements and units.
- Sampling plan, subgrouping, limits, and time window.
- Chart purpose and report audience.
Outputs
- Chart specification.
- Limit and formula checklist.
- Data-to-chart traceability requirements.
- Report summary with limitations.
Workflow
- Confirm raw process data and subgrouping before chart conclusions.
- Define chart type, axes, limits, and anomaly rules.
- Keep process symptoms separate from root cause.
- Pair charts with verification evidence.
Verification
- Check chart source fields and formulas.
- Check limits are defined and traceable.
- Check labels, legends, and anomaly indicators are readable.
Risks / Limits
- Missing raw process data blocks confirmed conclusions.
- Visual-only chart changes must not alter formulas.
- Capability interpretation requires appropriate data and assumptions.
Forbidden Actions
- Do not change formulas without disclosure.
- Do not present symptoms as root causes.
- Do not read protected paths or secrets.
Example Task
Create a chart spec for SPI solder paste volume control charts with verification criteria.
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.
- 1mo ago First seen · 51 lines · 25 tokens per session scan A cd20024d7e79
process-stat-chart is a skill published in the GitHub repository chenchihcu/DevSpace-MCP (0 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 312 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.
Other skills, from other repositories
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.