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 skills add edgedelta/claude-code-plugins --skill edgedelta-workflowsgit clone --depth 1 https://github.com/edgedelta/claude-code-pluginsWrote 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/edgedelta/claude-code-plugins/edgedelta-workflows)<a href="https://agentmods.dev/skills/edgedelta/claude-code-plugins/edgedelta-workflows"><img src="https://agentmods.dev/badge/skills/edgedelta/claude-code-plugins/edgedelta-workflows/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/edgedelta/claude-code-plugins/edgedelta-workflows"><img src="https://agentmods.dev/badge/skills/edgedelta/claude-code-plugins/edgedelta-workflows.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00048 | $0.01442 |
| Opus 5.5 | $0.00019 | $0.00577 |
| Sonnet 5.5 | $0.00010 | $0.00288 |
| Haiku 4.5 | $0.00005 | $0.00144 |
Grade A, and why
edgedelta-workflows 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 1mo 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EdgeDelta Workflows
Overview
Generate complete EdgeDelta workflow configurations — event-driven AI automation pipelines that connect monitors, external events, and schedules to AI teammates. Workflows are JSON DAGs with typed nodes (start, teammate, task, action, if-else, transform, set-state, note) executed on a distributed async engine.
Workflow Generation Process
1. Determine the Trigger
Ask what initiates the workflow:
| Trigger | Start Node Config | When to Use |
|---|---|---|
| Manual / Monitor / Connector | "start": {} |
Alert-driven, event-driven, or on-demand |
| Periodic (scheduled) | "start": { "periodicRun": { "schedule": { "cronExpression": "...", "timezone": "..." } } } |
Recurring health checks, reports |
2. Select the Template
Match the user's scenario to a template from references/templates.md:
| Scenario | Template |
|---|---|
| Alert → investigate → notify | Template 1 (Monitor Alert → Email) |
| Scheduled check with branching | Template 2 (Daily Health Check) |
| Full incident response (multi-tool) | Template 3 (Jira + Slack + PagerDuty) |
| Code review automation | Template 4 (PR Review → Slack) |
| Periodic reporting | Template 5 (Capacity → Teams) |
| Custom / none match | Build from scratch using schema |
3. Customize the Workflow
For each node, consult the appropriate reference:
- Node types and schemas: Read
references/workflow-schema.md - Action configurations: Read
references/action-types.md— covers all 29 action types with complete JSON examples - Templates: Read
references/templates.md— 5 production-tested starting points
4. Validate the Configuration
Before returning the workflow, verify:
- Exactly one
startnode exists - All node names match the pattern
/^[a-zA-Z0-9_-]+$/ - All node names are unique
- Every node (except
note) is referenced in at least one link - Every link references existing node names
- No cycles in the DAG
- If-else paths in links match the branch paths defined in the node
- Teammate nodes have a valid
agentId— built-in options:sre,devops-engineer,cloud-engineer,security-engineer,code-analyzer,issue-coordinator - Structured output schemas include
requiredand match JSON Schema spec - Action configs use the correct config key for the action type (e.g.,
slackSendMessageforslack-send-message) - Handlebars templates use triple braces
{{{ }}}for JSON/HTML content (no escaping) and double braces{{ }}for plain values - Integration names are user-provided — always ask if not specified
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.
- 1mo ago First seen · 128 lines · 48 tokens per session scan A a8ce1c05b3a4
edgedelta-workflows is a skill published in the GitHub repository edgedelta/claude-code-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 1,442 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.