api2pdf-automation

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

A connection for using Api2pdf, a service for creating PDF files through an API, via Rube MCP, a bridge between coding agents and external tools. It discovers the current tool instructions before running a task.

In plain words
What is it for?
It is for running Api2pdf operations from a coding agent after an active connection is set up.
Why use it?
It removes the need to manually wire a coding agent to Api2pdf or rely on possibly outdated input details.

Skill for Claude CodeCodex

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

Good fit It is for running Api2pdf operations from a coding agent after an active connection is set up.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/openteams-lab/openteams/api2pdf-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 api2pdf-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 api2pdf-automation

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/openteams-lab/openteams/api2pdf-automation"><img src="https://agentmods.dev/badge/skills/openteams-lab/openteams/api2pdf-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 743 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.00029 $0.00743
Opus 5 $0.00015 $0.00371
Sonnet 5 $0.00006 $0.00149
Haiku 4.5 $0.00003 $0.00074

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

Security

Grade A, and why

api2pdf-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 11d 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/api2pdf-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.

Api2pdf Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/api2pdf

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Api2pdf connection via RUBE_MANAGE_CONNECTIONS with toolkit api2pdf
  • 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 api2pdf
  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: "Api2pdf 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 Api2pdf task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["api2pdf"]
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. 11d ago First seen · 92 lines · 29 tokens per session scan A 4762f40e62cc

Subscribe to this mod's changes

api2pdf-automation is a skill published in the GitHub repository openteams-lab/openteams (612 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 743 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

foundry-hosted-agent-validation

Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.

microsoft/agent-framework · 82 tokens

papyrus-diagnose-compilation

Diagnose and fix LaTeX compilation failures. Use when the document does not compile, pdflatex/bibtex/biber/tectonic errors out, the PDF is stale, or the author reports a build/compile error in the Papyrus editor.

kirodotdev/KiroCrew · 60 tokens

document-processor

Guidance for processing documents, extracting content, and transforming structured information. Use when the user asks to process, parse, extract, or transform document content such as PDFs, Word files, or spreadsheets.

vixues/LeAgent · 44 tokens

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…

awslabs/agentcore-samples · 92 tokens

create-pdf

Guidelines for creating polished, themed PDF reports with the code execution tool.

aws-samples/sample-ai-assistant-on-agentcore · 18 tokens

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…

InstantNeo/instantneo · 92 tokens