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/pulse-createnpx skills add Pulse-Intelligence/pulse-workflow-mcp --skill pulse-creategit 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-create)<a href="https://agentmods.dev/skills/pulse-intelligence/pulse-workflow-mcp/pulse-create"><img src="https://agentmods.dev/badge/skills/pulse-intelligence/pulse-workflow-mcp/pulse-create.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.00064 | $0.01133 |
| Opus 5 | $0.00032 | $0.00566 |
| Sonnet 5 | $0.00013 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
pulse-create 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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pulse Workflow
Build a complete workflow from a description. Uses discovery-first approach.
Usage
/pulse-create <description>
Example:
/pulse-create customer support chatbot with knowledge base
/pulse-create RAG pipeline for product documentation
/pulse-create API integration that fetches weather data
Workflow Creation Process
Phase 1: Discovery (MANDATORY)
Before creating anything, discover available capabilities:
# 1. List/select or create app
list_apps(mode="workflow")
# If existing app: select_app(app_id="...")
# If new: create_app(name="<from description>", mode="workflow")
# 2. Discover what's available
list_node_types() # Available node types
list_models(model_type="llm") # Available AI models
list_datasets() # Available knowledge bases (if RAG needed)
list_tool_providers() # Available tools (if integrations needed)
# 3. Get schemas for nodes you'll use
get_node_schema(block_type="llm")
get_node_schema(block_type="knowledge-retrieval") # if RAG
get_node_schema(block_type="http-request") # if API
get_node_schema(block_type="code") # if transform
Phase 2: Plan the Workflow
Based on the description, identify:
- Entry point: Always
startnode (usually exists) - Processing nodes: What processing is needed?
- Simple chat →
llm - RAG →
knowledge-retrieval→llm - Classification →
question-classifier→ branches - API call →
http-request→code(transform)
- Simple chat →
- Exit point:
answer(chat) orend(return data)
Phase 3: Build Incrementally
Critical Rule: Add ONE node at a time, verify, then continue.
# Get current state
view_workflow()
nodes = list_nodes()
start_id = <find start node id>
# Add first processing node
result = add_node(
node_type="...",
title="...",
config={...}, # From schema, use defaults where possible
after_node_id=start_id
)
node1_id = result["node_id"]
# Verify it was added
view_workflow()
# Add second node
result = add_node(
node_type="...",
config={...},
after_node_id=node1_id
)
node2_id = result["node_id"]
# Continue until complete...
# Add answer/end node
add_node(
node_type="answer",
config={"answer": "{{#<last_node_id>.output#}}"},
after_node_id=node2_id
)
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.
- 3d ago First seen · 180 lines · 64 tokens per session scan A 718284623f4d
pulse-create is a skill published in the GitHub repository Pulse-Intelligence/pulse-workflow-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 64 tokens to every session and 1,133 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…