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 travisjneuman/.claude --skill process-flowchart-designergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/process-flowchart-designer)<a href="https://agentmods.dev/skills/travisjneuman/.claude/process-flowchart-designer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/process-flowchart-designer/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/travisjneuman/.claude/process-flowchart-designer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/process-flowchart-designer.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.00037 | $0.03077 |
| Opus 5.5 | $0.00015 | $0.01231 |
| Sonnet 5.5 | $0.00007 | $0.00615 |
| Haiku 4.5 | $0.00004 | $0.00308 |
Grade A, and why
process-flowchart-designer 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 16d 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Flowchart Designer
Frameworks for translating business processes into clear visual diagrams, identifying inefficiencies, and designing optimized workflows.
Flowchart Notation
Standard Symbols
FLOWCHART SYMBOL REFERENCE:
┌─────────┐
│ Rectangle│ = Process / Action step
└─────────┘
◇ Diamond = Decision point (Yes/No, True/False)
┌─────────┐
│/ Parallel/│ = Parallelogram = Input/Output
└─────────┘
( Oval ) = Start / End (Terminal)
┌─────────┐
│ Cylinder │ = Database / Data store
└─────────┘
┌─────────┐
│ Document │ = Document / Report
└~~~~~~~~~~┘
○ Circle = Connector (links to another part)
→ Arrow = Flow direction
Text-Based Flowchart Template
PROCESS FLOWCHART: [Process Name]
Version: [X.X]
Owner: [Department/Role]
Last Updated: [Date]
( START )
│
▼
┌──────────────┐
│ Step 1: │
│ [Action] │
└──────┬───────┘
│
▼
◇ Decision?
/ \
Yes No
│ │
▼ ▼
┌────┐ ┌────┐
│ A │ │ B │
└──┬─┘ └──┬─┘
│ │
└──┬───┘
│
▼
( END )
Process Mapping
Process Documentation Template
PROCESS MAP: [Name]
METADATA:
Process Owner: [Name/Role]
Department: [Department]
Frequency: [Daily/Weekly/Monthly/Ad hoc]
Average Duration: [Time]
Trigger: [What initiates this process]
Output: [What the process produces]
STEPS:
# | Step Name | Actor | Action | System/Tool | Duration | Notes
---|--------------------| ------------|----------------------|-------------|----------|------
1 | [Name] | [Role] | [What they do] | [Tool] | [Time] |
2 | [Name] | [Role] | [What they do] | [Tool] | [Time] |
3 | DECISION: [Query] | [Role] | [Evaluate criteria] | [Tool] | [Time] |
3a | [If Yes] | [Role] | [Action] | [Tool] | [Time] |
3b | [If No] | [Role] | [Action] | [Tool] | [Time] |
4 | [Name] | [Role] | [What they do] | [Tool] | [Time] |
HANDOFFS:
From → To | Trigger | Method
[Role A] → [Role B] | [When] | [Email/System/etc.]
EXCEPTIONS:
Exception | Handling Procedure | Escalation Path
[What can go wrong] | [What to do] | [Who to contact]
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.
- 16d ago First seen · 351 lines · 37 tokens per session scan A f8a72ad62f72
process-flowchart-designer is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 3,077 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-09-30.
Other skills, from other repositories
pick-up
Reads the newest entry of a project's log.md and tells the student where they left off: what they did and decided, what is open, and the next step. Takes an optional project name. With several projects and no name, shows a menu of each project's last entry. Read only. Use when the student says pick up, where did I…
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.
Google Calendar
View, create, update, and delete Google Calendar events. Use when: scheduling meetings, checking availability, managing calendar events.
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.