abstract-automation

abstract-automation is a skill for Claude Code, Codex from openteams-lab/openteams. It costs 25 tokens per session (715 once invoked), scanned A, a copy of ably-automation, Apache-2.0.

An automation guide for Abstract, a collaborative design and version-control tool, through connected automation tools.

In plain words
What is it for?
Use it to find current Abstract tools, connect an Abstract account, and run supported Abstract workflows.
Why use it?
It helps an agent discover the currently available actions and confirm the required connection before trying to automate Abstract work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to find current Abstract tools, connect an Abstract account, and run supported Abstract workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openteams-lab/openteams/abstract-automation
Install

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.

Any agent
npx skills add openteams-lab/openteams --skill abstract-automation
Clone the repo
git clone --depth 1 https://github.com/openteams-lab/openteams

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for abstract-automation

README.md
[![agentmods](https://agentmods.dev/badge/skills/openteams-lab/openteams/abstract-automation/github.svg)](https://agentmods.dev/skills/openteams-lab/openteams/abstract-automation)
Your own site
<a href="https://agentmods.dev/skills/openteams-lab/openteams/abstract-automation"><img src="https://agentmods.dev/badge/skills/openteams-lab/openteams/abstract-automation/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.

agentmods 80×15 button for abstract-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/openteams-lab/openteams/abstract-automation"><img src="https://agentmods.dev/badge/skills/openteams-lab/openteams/abstract-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 715 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.00715
Opus 5 $0.00013 $0.00358
Sonnet 5 $0.00005 $0.00143
Haiku 4.5 $0.00003 $0.00072

Measured 12d ago against content hash df50052f4cdf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

abstract-automation 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 12d 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.

Origin

This is a copy

86% identical to ably-automation — 24 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.

assets/skills/abstract-automation/SKILL.md · 92 lines

How it starts

The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Abstract Automation via Rube MCP

Automate Abstract operations through Composio's Abstract toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/abstract

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Abstract connection via RUBE_MANAGE_CONNECTIONS with toolkit abstract
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit abstract
  3. If connection is not ACTIVE, follow the returned auth link to complete setup
  4. Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Abstract operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Abstract task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["abstract"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

  • Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  • Schema compliance: Use exact field names and types from the search results
  • Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
  • Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
  • Pagination: Check responses for pagination tokens and continue fetching until complete

Read the full file on GitHub · 92 lines

Changes

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.

  1. 12d ago First seen · 92 lines · 25 tokens per session scan A df50052f4cdf

Subscribe to this mod's changes

abstract-automation is a skill published in the GitHub repository openteams-lab/openteams (612 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to ably-automation, differing in 24 lines, and is treated as a copy.

Related

Other skills, from other repositories

brand-landingpage

Brand-first landing page designer — runs a brand-identity interview (colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML. Use when the user asks to create, design, or build a landing page, homepage, or marketing page and has no established…

wshobson/agents · 112 tokens

design-critique

Run a heuristic evaluation of a UI design (image, HTML, Figma, URL, or flow) the way an experienced designer would. Evaluates 4 categories (Visual & hierarchy, Usability & interaction, Accessibility, Content) using recognized frameworks, NN/g 0-4 severity, and evaluability-aware prioritization that never judges what…

kirodotdev/KiroCrew · 131 tokens

theme-pack-authoring

Build, validate, and install Kiro Crew theme packs -- pack anatomy, the 56-variable palette, role-tagged fonts, the overrides.css allowlist (what installs vs what actually renders), and the install-verify cycle. Use when the user wants to create or edit a theme pack.

kirodotdev/KiroCrew · 64 tokens

image-authoring

Author images and diagrams as code — SVG, Pillow, Excalidraw, mermaid. Load when asked to draw, illustrate, or make an image, icon, logo, poster, or diagram.

kirodotdev/KiroCrew · 45 tokens

frontend-design-workflow

Workflow for frontend features, visual changes, and product design changes. Present mockup options before writing code, build against the project's design system, capture the right evidence type (screenshots vs video), and run a new-user usability review before finalizing. Use when building or changing UI, styling…

kirodotdev/KiroCrew · 75 tokens

new-feature-design

Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and…

agentic-community/mcp-gateway-registry · 118 tokens