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/hoavdc/codexkit/codexkit-process-mappernpx skills add hoavdc/CodexKit --skill codexkit-process-mappergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-process-mapper)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-process-mapper"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-process-mapper.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.00073 | $0.01066 |
| Opus 5 | $0.00036 | $0.00533 |
| Sonnet 5 | $0.00015 | $0.00213 |
| Haiku 4.5 | $0.00007 | $0.00107 |
Grade A, and why
codexkit-process-mapper 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 yesterday.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Mapper
Purpose
Document and analyze business processes to find waste, reduce cycle time, and identify automation or improvement opportunities.
When to use
- mapping an existing process for documentation (SOP creation)
- analyzing a process for waste or bottleneck elimination
- preparing for process automation — need to map "as-is" before designing "to-be"
- onboarding new team members who need to understand workflows
When not to use
- software system architecture (use engineering architecture tools)
- strategic planning or roadmapping
- one-time checklists with no recurring flow
Inputs
- process name and scope (start trigger, end event)
- stakeholders involved (roles, departments)
- current steps and their sequence (rough list is fine)
- known pain points, bottlenecks, or complaints
- approximate time per step (if known)
- any existing documentation or SOPs
Procedure
- Define scope: specify the start trigger, end event, and boundaries.
- Map "as-is" process in swimlane format:
- Rows = roles or departments (who does what)
- Columns = process phases
- Symbols: Rounded Rectangle = Activity, Diamond = Decision, Arrow = Flow, Circle = Start/End
- Document each step:
- Step name (action verb + object)
- Owner (role, not person name)
- Estimated time
- Input and output artifacts
- Systems or tools used
- Identify the 8 Lean Wastes (DOWNTIME):
- Defects: errors requiring rework
- Overproduction: doing more than needed
- Waiting: idle time between steps
- Non-utilized talent: underusing people's skills
- Transportation: unnecessary movement of information or work
- Inventory: work piling up between steps (WIP)
- Motion: unnecessary steps or clicks
- Extra processing: over-engineering, gold-plating
- Calculate process metrics:
- Total cycle time (start to end)
- Value-added time vs. non-value-added time
- Process efficiency = Value-added time / Total cycle time × 100%
- Number of handoffs between roles
- Recommend improvements (prioritized by impact vs. effort):
- Eliminate: remove waste steps
- Automate: replace manual steps with tools
- Simplify: reduce decision points or approvals
- Parallelize: run independent steps concurrently
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 115 lines · 73 tokens per session scan A 48bc7d6c3102
codexkit-process-mapper is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,066 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-09-03.
Other skills, from other repositories
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
product-reviews
Help users design and facilitate product reviews that shift from status updates to strategic deep-dives, ensuring high-quality craftsmanship and organizational alignment.
delivering-delegated-linear-issues
当用户明确要求领取、处理、批量清空或定时扫描 Linear 的 Delegated to Agent issue 时使用；按队列状态、领取竞争、交付路径和收尾四个阶段渐进读取。.
github-issues
Create, manage, triage, and close GitHub issues. Search existing issues, add labels, assign people, and link to PRs. Works with gh CLI or falls back to git + GitHub REST API via curl.
analyzing-changes
Analyzes code changes, detects documentation drift, and evaluates change impact scope. Use when reviewing diffs, checking doc sync, or running pre-commit analysis. Automatically triggered after design-level changes or refactoring.
analyzing-security
Scans code for security vulnerabilities, detects dangerous patterns, and ensures security decisions are documented. Use when running security scans, auditing code, or checking for OWASP issues, injection risks, or sensitive data leaks. Automatically triggered on new modules, security-related changes, or post-refactor.