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 zai-org/Synapse --skill automation-workflowsgit clone --depth 1 https://github.com/zai-org/SynapseWrote 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/zai-org/synapse/automation-workflows)<a href="https://agentmods.dev/skills/zai-org/synapse/automation-workflows"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/automation-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/zai-org/synapse/automation-workflows"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/automation-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 219 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00105 | $0.02469 |
| Opus 5.5 | $0.00042 | $0.00988 |
| Sonnet 5.5 | $0.00021 | $0.00494 |
| Haiku 4.5 | $0.00011 | $0.00247 |
Grade A, and why
automation-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.
Copies of this mod
3 near-identical copies found in the catalogue:
- automation-workflows — 100% identical, 0 lines differ
- automation-workflows — 100% identical, 0 lines differ
- automation-workflows — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automation Workflows
Overview
As a solopreneur, your time is your most valuable asset. Automation lets you scale without hiring. The goal is simple: automate anything you do more than twice a week that doesn't require creative thinking. This playbook shows you how to identify automation opportunities, design workflows, and implement them without writing code.
Step 1: Identify What to Automate
Not every task should be automated. Start by finding the highest-value opportunities.
Automation audit (spend 1 hour on this):
-
Track every task you do for a week (use a notebook or simple spreadsheet)
-
For each task, note:
- How long it takes
- How often you do it (daily, weekly, monthly)
- Whether it's repetitive or requires judgment
-
Calculate time cost per task:
Time Cost = (Minutes per task × Frequency per month) / 60Example: 15 min task done 20x/month = 5 hours/month
-
Sort by time cost (highest to lowest)
Good candidates for automation:
- Repetitive (same steps every time)
- Rule-based (no complex judgment calls)
- High-frequency (daily or weekly)
- Time-consuming (takes 10+ minutes)
Examples:
- ✅ Sending weekly reports to clients (same format, same schedule)
- ✅ Creating invoices after payment
- ✅ Adding new leads to CRM from form submissions
- ✅ Posting social media content on a schedule
- ❌ Conducting customer discovery interviews (requires nuance)
- ❌ Writing custom proposals for clients (requires creativity)
Low-hanging fruit checklist (start here):
- Email notifications for form submissions
- Auto-save form responses to spreadsheet
- Schedule social posts in advance
- Auto-create invoices from payment confirmations
- Sync data between tools (CRM ↔ email tool ↔ spreadsheet)
Step 2: Choose Your Automation Tool
Three main options for no-code automation. Pick based on complexity and budget.
Tool comparison:
| Tool | Best For | Pricing | Learning Curve | Power Level |
|---|---|---|---|---|
| Zapier | Simple, 2-3 step workflows | $20-50/month | Easy | Low-Medium |
| Make (Integromat) | Visual, multi-step workflows | $9-30/month | Medium | Medium-High |
| n8n | Complex, developer-friendly, self-hosted | Free (self-hosted) or $20/month | Medium-Hard | High |
What ships with it
2 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 · 268 lines · 105 tokens per session scan A 7e2a1b38c6f3
automation-workflows is a skill published in the GitHub repository zai-org/Synapse (501 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 105 tokens to every session and 2,469 once invoked, about $0.0004 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.