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/pulse-intelligence/pulse-workflow-mcp/pulsenpx skills add Pulse-Intelligence/pulse-workflow-mcp --skill pulsegit clone --depth 1 https://github.com/Pulse-Intelligence/pulse-workflow-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/pulse-intelligence/pulse-workflow-mcp/pulse)<a href="https://agentmods.dev/skills/pulse-intelligence/pulse-workflow-mcp/pulse"><img src="https://agentmods.dev/badge/skills/pulse-intelligence/pulse-workflow-mcp/pulse.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.00061 | $0.00922 |
| Opus 5 | $0.00030 | $0.00461 |
| Sonnet 5 | $0.00012 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
pulse 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pulse Workflow Development
Build and manage Pulse (Dify) workflows using MCP tools directly from Claude Code.
Available Commands
| Command | Description |
|---|---|
/pulse |
This help - overview and concepts |
/pulse-create |
Create a new workflow from description |
/pulse-edit |
Edit an existing workflow |
/pulse-publish |
Validate and publish workflow |
Quick Start
1. /pulse-create customer support chatbot with RAG
2. /pulse-edit # Make changes
3. /pulse-publish # Validate & publish
Core Concepts
Workflows
Workflows are visual pipelines of connected nodes that process user input and generate responses. Each workflow belongs to an app.
Nodes
Processing units in a workflow:
- Control: start, end, answer, if-else, iteration, loop
- AI: llm, knowledge-retrieval, question-classifier, parameter-extractor
- Transform: code, template-transform, variable-assigner, variable-aggregator
- External: http-request, tool
Edges
Connections between nodes defining data flow. Each edge connects a source node's output handle to a target node's input handle.
MCP Tools Available
The pulse-workflow MCP server provides these tools:
Discovery (ALWAYS use first)
list_node_types- Get available node typesget_node_schema- Get node configuration schemalist_models- Get available AI modelslist_datasets- Get knowledge baseslist_tool_providers/list_tools- Get external tools
App Management
list_apps- List available appsselect_app- Select app to work withcreate_app- Create new appinitialize_workflow- Initialize workflow for new app (auto-called by create_app)
Workflow Operations
view_workflow- See current structurevalidate_workflow- Check for errorspublish_workflow- Publish draft
Node Operations
add_node- Add node to workflowedit_node- Modify node configdelete_node- Remove nodeget_node/list_nodes- View nodesbatch_add_nodes- Add multiple nodes in one call (efficient)
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.
- 2d ago First seen · 110 lines · 61 tokens per session scan A 55ca80dab058
pulse is a skill published in the GitHub repository Pulse-Intelligence/pulse-workflow-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 922 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…