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 instructions/pulse-intelligence/pulse-workflow-mcp/claude-mdgit 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/instructions/pulse-intelligence/pulse-workflow-mcp/claude-md)<a href="https://agentmods.dev/instructions/pulse-intelligence/pulse-workflow-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/pulse-intelligence/pulse-workflow-mcp/claude-md.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.00988 | $0.00988 |
| Opus 5 | $0.00494 | $0.00494 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
pulse-workflow-mcp CLAUDE.md 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is an MCP (Model Context Protocol) server that enables Claude Code to interact with Pulse workflows. It exposes Pulse workflow operations as MCP tools, allowing workflow creation, node management, edge connections, and publishing.
Development Commands
# Install dependencies (editable mode)
pip install -e ".[dev]"
# or with uv
uv pip install -e ".[dev]"
# Run the server locally
python -m pulse_workflow_mcp
# Run tests
pytest tests/
# Run a single test
pytest tests/test_server.py::TestConfig::test_config_defaults
Environment Variables
export PULSE_API_URL="http://localhost:5001" # Pulse instance URL
export PULSE_API_KEY="your-api-key" # Console API key (required)
export PULSE_APP_ID="your-app-id" # Optional: default app ID
Architecture
src/pulse_workflow_mcp/
├── server.py # Main MCP server, tool definitions, and call_tool handler
├── dify_client.py # PulseClient - HTTP client for Pulse API operations
├── config.py # Configuration via pydantic-settings
├── prompts/ # MCP prompt templates (workflow_context, discovery, etc.)
└── resources/ # MCP resources (workflow state, node type schemas)
Key Components
server.py: Defines all MCP tools (40+ tools) in _get_all_tools() and routes tool calls in call_tool(). Tools are organized into categories:
- App management:
list_apps,select_app,create_app - Node operations:
add_node,edit_node,delete_node,batch_add_nodes - Edge operations:
connect_nodes,disconnect_nodes - Discovery:
list_node_types,get_node_schema,list_models,list_datasets - Workflow:
view_workflow,validate_workflow,publish_workflow
dify_client.py: PulseClient class handles all Pulse API communication. Key methods:
- Workflow CRUD via
get_workflow(),sync_workflow(),publish_workflow() - Node/edge manipulation through graph operations
- Auto-initializes workflows for new apps with start node (and LLM+answer for advanced-chat mode)
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 · 112 lines · 988 tokens per session scan A 6d9d0616cc2a
pulse-workflow-mcp CLAUDE.md is an instructions file published in the GitHub repository Pulse-Intelligence/pulse-workflow-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 988 tokens to every session, about $0.0049 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 instructions, from other repositories
ESAA-Core AGENTS.md
Instructions for elzobrito/ESAA-Core, covering agents.md — contrato operacional codex/esaa, 1. autoridade e termos, 2. cli e runner, ou configure o runner uma vez por sessão and 3. concorrência.
Kanvas AGENTS.md
Instructions for XMihura/Kanvas, covering canvas workflow — agent instructions, critical rule, session protocol, 1. start of session — read the board and 2. pick a task.
delivery-loop CLAUDE.md
Instructions for blakemartz/delivery-loop, covering claude.md, what this is, the cardinal rule: everything must stay repo-agnostic, layout and config: the one seam.
taskcenter AGENTS.md
AGENTS.md instructions for xiaogezi/taskcenter, covering taskcenter agent rules, safety boundaries, required workflow and verification.
idd-skill idd-resume.instructions.md
Instructions for kurone-kito/idd-skill, covering idd — resume phase, required inputs, step 0 — route classifier, operator-present release and step 1 — identify claim state.
kanban-lite AGENTS.md
AGENTS.md instructions for borgius/kanban-lite, covering kanban markdown - development guide, repo-wide defaults and post-change verification (mandatory).