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 stunt-double/stuntdouble-mcp --skill maintain-automationsgit clone --depth 1 https://github.com/stunt-double/stuntdouble-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/stunt-double/stuntdouble-mcp/maintain-automations)<a href="https://agentmods.dev/skills/stunt-double/stuntdouble-mcp/maintain-automations"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/maintain-automations/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/stunt-double/stuntdouble-mcp/maintain-automations"><img src="https://agentmods.dev/badge/skills/stunt-double/stuntdouble-mcp/maintain-automations.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.00043 | $0.00576 |
| Opus 5.5 | $0.00017 | $0.00230 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
maintain-automations 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 18d 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
86% identical to artifacts — 107 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.
What it actually says
Maintain automations
- Find and read:
search(workspace_id, query),list_workflows,list_checklists.get_workflow(workflow_id)shows steps, connections,execution_orderandunreachable_step_ids; read it before changing anything. - Trigger and details:
update_workflow(workflow_id, name?, description?, trigger_config?). For a schedule send{ cron, timezone }with the timezone fromget_me. - Steps:
update_workflow_step(step_id, config)replaces the config in full: send every key.add_workflow_step(...)appends and connects;remove_workflow_step(step_id)repoints its inputs at its outputs.reorder_workflow_steps(workflow_id, step_ids)sets one linear order. Pass every id (one left out is disconnected); it flattens branches.
- Branches:
connect_workflow_steps(workflow_id, source_step_id, target_step_id, branch). On a condition stepbranchis'true'or'false'; otherwisenull. A step appended after a condition lands ontrue;falseis unconnected by default, so a failed condition ends the run unless you connect it.source_step_id: nullis the trigger;target_step_id: nulldisconnects. - Checklists:
get_checklist(checklist_id), thenupdate_checklist(checklist_id, checks=[…])sending each existing check with itsid. A kept id keeps run history; a dropped check is deleted with its results. Also adjustable:instructions,url,actor_id,pass_threshold,run_mode. - Verify:
get_workflowagain (all steps inexecution_order, none unreachable), thenrun_workfloworrun_checklistonce. - Pause or retire: prefer
toggle_workflowto pause.delete_workflowanddelete_checklistdiscard all run history, so use them only when the user asks.
Example, notify only on failure: add_workflow_step(workflow_id, step_type="condition", config={ field: "previous_step.failed", operator: "gt", value: 0 }), then add_workflow_step(workflow_id, step_type="notification", config={ channel: "email", recipients: { type: "all_members" }, template: "failed" }).
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.
- 18d ago Changed · -60 lines · -7 tokens per session 710381939c5c
- 1mo ago First seen · 80 lines · 50 tokens per session scan A 1e4bb13cabba
maintain-automations is a skill published in the GitHub repository stunt-double/stuntdouble-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 576 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to artifacts, differing in 107 lines, and is treated as a copy.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.