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-editnpx skills add Pulse-Intelligence/pulse-workflow-mcp --skill pulse-editgit 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-edit)<a href="https://agentmods.dev/skills/pulse-intelligence/pulse-workflow-mcp/pulse-edit"><img src="https://agentmods.dev/badge/skills/pulse-intelligence/pulse-workflow-mcp/pulse-edit.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.00060 | $0.01553 |
| Opus 5 | $0.00030 | $0.00776 |
| Sonnet 5 | $0.00012 | $0.00311 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
pulse-edit 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit Pulse Workflow
Modify an existing workflow with PATCH-style updates.
Usage
/pulse-edit
/pulse-edit <specific change description>
Examples:
/pulse-edit change the LLM model to Claude
/pulse-edit add error handling to the API call
/pulse-edit remove the classification step
/pulse-edit connect node X to node Y
Edit Workflow Process
Step 1: Understand Current State
Always start by viewing the current workflow:
# Ensure correct app is selected
list_apps(mode="workflow")
select_app(app_id="...")
# View complete structure
view_workflow(include_details=True)
# List all nodes
list_nodes()
# List all connections
list_edges()
Step 2: Identify Changes Needed
Based on the edit request, determine:
- Node modifications: Change config, title, or position
- Node additions: Add new nodes to the flow
- Node deletions: Remove nodes (and their edges)
- Connection changes: Add/remove edges between nodes
- Restructuring: Reorder or reroute the flow
Step 3: Apply PATCH-Style Updates
Critical Rule: Only change what needs to change. Don't recreate nodes unnecessarily.
Common Edit Operations
Modify Node Configuration
# 1. Get current node state
node = get_node(node_id="target-node-id")
# 2. Get schema to understand options
get_node_schema(block_type=node["data"]["type"])
# 3. Apply PATCH update - only changed fields
edit_node(
node_id="target-node-id",
config={
# Only include fields you're changing
"model": {
"name": "claude-3-opus" # Just changing model name
}
}
)
Change Node Title
edit_node(
node_id="target-node-id",
title="New Descriptive Title"
)
Update Node Position
edit_node(
node_id="target-node-id",
position={"x": 300, "y": 150}
)
Add a Node Between Existing Nodes
# Current: A → B
# Desired: A → NEW → B
# 1. Find the edge to break
edges = list_edges()
edge_to_remove = <find A→B edge>
# 2. Remove old connection
disconnect_nodes(source_id="A", target_id="B")
# 3. Add new node
result = add_node(
node_type="...",
config={...},
after_node_id="A"
)
new_node_id = result["node_id"]
# 4. Connect new node to B
connect_nodes(source_id=new_node_id, target_id="B")
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 · 294 lines · 60 tokens per session scan A bf6db6688d11
pulse-edit is a skill published in the GitHub repository Pulse-Intelligence/pulse-workflow-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 60 tokens to every session and 1,553 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
okx-task-watch
监听任务进展 / 帮我盯着任务 / 任务有动静告诉我 / 历史消息 / 未读消息 / 未决策 / 待决策 / 继续监听 / task watch / user watch / monitor task progress / catch me up on tasks / outstanding decisions — OKX A2A user-session task-notification monitor: live long-poll via okx-a2a user watch (also drains backlog of past/missed/unread events on entry) plus…
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.