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 MerkyorLynn/Lynn --skill automation-workflowsgit clone --depth 1 https://github.com/MerkyorLynn/LynnWrote 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/merkyorlynn/lynn/automation-workflows)<a href="https://agentmods.dev/skills/merkyorlynn/lynn/automation-workflows"><img src="https://agentmods.dev/badge/skills/merkyorlynn/lynn/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/merkyorlynn/lynn/automation-workflows"><img src="https://agentmods.dev/badge/skills/merkyorlynn/lynn/automation-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.00105 | $0.02469 |
| Opus 5 | $0.00053 | $0.01234 |
| Sonnet 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 10d 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.
This is a copy
100% identical to automation-workflows — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
1 file 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.
- 10d ago First seen · 268 lines · 105 tokens per session scan A 7e2a1b38c6f3
automation-workflows is a skill published in the GitHub repository MerkyorLynn/Lynn (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 105 tokens to every session and 2,469 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to automation-workflows, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
loop
Create a loop that runs a prompt now and follows up either on a fixed schedule or through self-paced wakeups. Usage - /loop check the build, /loop 5m check the build, /loop check the PR every 30m. /loop list to show jobs, /loop clear to cancel all.
session-reader
Summarize Mux session folders into a clean markdown report. Use when you need fast context at task start, want to review tool calls, delegated agents, artifacts, or outcomes across one or more sessions.
cua-driver
Drive a native GUI app (macOS, Windows, Linux) via the Qwen Cua Driver CLI (default) or MCP server; snapshot its accessibility tree, act through snapshot-bound element tokens, native menu paths, exact window geometry, or pixel coordinates, and verify from fresh state. Use when the user asks you to operate, drive…
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
goal-draft
Turn a fuzzy intention into a /goal objective the Goal verifier can actually judge - one outcome, numbered binary "Done when" checks that leave evidence in the transcript, guardrails, a budget, and a block protocol. Use when the user wants to set or define a goal, asks whether a goal is good enough, or says "keep…