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/proxy2021/enso/workflow_mappernpx skills add Proxy2021/Enso --skill workflow_mappergit clone --depth 1 https://github.com/Proxy2021/EnsoWhat 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.00028 | $0.00923 |
| Opus 5 | $0.00014 | $0.00462 |
| Sonnet 5 | $0.00006 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
workflow_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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow integration mapper — inventory your daily tools, map workflows, discover Enso integration opportunities, and build automation rules to eliminate friction
Tool Reference
enso_workflow_mapper_browse (primary)
View your workflow profile: tool inventory summary, mapped workflows, integration score, and automation rules. Use when the user says: 'open workflow mapper', 'show my workflows', 'workflow dashboard', 'integration planner', 'show my tools'.
enso_workflow_mapper_inventory
Add, remove, or update tools in your daily tool inventory. Specify category, frequency, use case, and pain points for each tool. Use when the user says: 'add a tool', 'I use Slack', 'update my tools', 'remove tool', 'edit tool inventory'.
Parameters:
action(string): Action: add, remove, update, listname(string): Tool name (e.g. Gmail, Slack, GitHub, Notion, Calendar)category(string): Category: Communication, Productivity, Development, Media, Finance, Otherfrequency(string): Usage frequency: daily, weekly, monthlyuseCase(string): Primary use case in 1-3 wordspainPoints(string): Optional friction or pain points with this tooltoolId(string): Tool ID for remove/update actions
enso_workflow_mapper_map_workflow
Create or edit a daily workflow mapping with ordered steps, tools used, time estimates, and friction points. Use template names like 'Morning routine', 'Work deep focus', 'Meeting prep', 'End of day review', 'Weekend planning'. Use when the user says: 'map a workflow', 'create workflow', 'morning routine', 'map my process', 'add workflow steps'.
Parameters:
action(string): Action: create, view, add_step, remove_step, deletename(string): Workflow nametemplate(string): Template: morning_routine, deep_focus, meeting_prep, end_of_day, weekend_planning, blankworkflowId(string): Workflow ID for view/edit/delete actionsstepLabel(string): Step description for add_stepstepTool(string): Tool used at this step for add_stepstepMinutes(number): Estimated minutes for this stepstepFriction(string): Friction/pain point at this step (optional)stepId(string): Step ID for remove_step
What ships with it
8 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 · 68 lines · 28 tokens per session scan A f3444d3eddf0
workflow_mapper is a skill published in the GitHub repository Proxy2021/Enso (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 923 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.
Other skills, from other repositories
clawteam
Multi-agent swarm orchestration. USE THIS (not delegatetask) when the user says team/swarm/multi-agent/clawteam/parallel-agents/agent-team, or asks for multi-perspective analysis (stocks, research, code review, strategy). Spawns N Hermes workers in tmux windows with git worktree isolation, file-based inboxes, and a…
clawteam
Multi-agent swarm coordination via the ClawTeam CLI. Use when the user wants to create agent teams, spawn multiple agents to work in parallel, coordinate tasks with dependencies, broadcast messages between agents, monitor progress via kanban board, or launch pre-built team templates (hedge-fund, code-review…
openclaw-plugin
This plugin is a thin adapter between OpenClaw and LycheeMem. It does not replace memory-core, does not claim plugins.slots.memory, and does not duplicate LycheeMem algorithms.
lycheemem
Forceful operating rules for using LycheeMem as the primary structured long-term memory path inside OpenClaw.
memory
Use LycheeMem as Claude Code's structured long-term memory for prior conversations, user preferences, project decisions, timelines, and durable facts.
tweetclaw
OpenClaw guide for Twitter search, follower exports, monitoring, media, and approved X automation through Xquik. Not affiliated with X Corp.