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 lunchpaillola/pipa-skills --skill pipa-connectorsgit clone --depth 1 https://github.com/lunchpaillola/pipa-skillsWrote 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/lunchpaillola/pipa-skills/pipa-connectors)<a href="https://agentmods.dev/skills/lunchpaillola/pipa-skills/pipa-connectors"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-connectors/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/lunchpaillola/pipa-skills/pipa-connectors"><img src="https://agentmods.dev/badge/skills/lunchpaillola/pipa-skills/pipa-connectors.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.00035 | $0.01416 |
| Opus 5 | $0.00017 | $0.00708 |
| Sonnet 5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
pipa-connectors 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipa Connectors
Set up, inspect, explain, or troubleshoot Pipa connected tools.
Mental Model
- This is an operation, not a business lane.
pipa-manageroutes Pipa configuration; this skill owns connector setup and status.- Business lanes own the job;
composio-mcpperforms live app discovery, authorization, and actions. ~/.pipa/CONNECTORS.mdrecords selected capability-to-tool mappings. Composio remains the source of truth for live connection status.- The
~~prefix marks a capability placeholder resolved through the global map; it is not a toolkit slug.
Capability Categories
~~chat,~~email,~~calendar,~~project tracker~~code hosting,~~knowledge base,~~cloud storage,~~CRM~~support platform,~~content platform,~~payments,~~time tracking
Lane Map
| Pipa lane | Common connector categories |
|---|---|
| Get work | ~~CRM, ~~email, ~~chat, ~~project tracker, ~~content platform, ~~knowledge base |
| Define work | ~~email, ~~chat, ~~knowledge base, ~~cloud storage, ~~project tracker, ~~code hosting, ~~calendar |
| Deliver work | ~~project tracker, ~~chat, ~~code hosting, ~~calendar, ~~knowledge base |
| Get paid | ~~payments, ~~time tracking, ~~email, ~~CRM, ~~calendar |
| Keep clients | ~~CRM, ~~email, ~~chat, ~~calendar, ~~project tracker, ~~support platform |
| Improve operations | ~~knowledge base, ~~cloud storage, ~~code hosting, ~~project tracker, ~~calendar, ~~chat, ~~email |
Review The Global Connector Map
- Read
~/.pipa/CONNECTORS.mdwhen present. - Use
composio-mcpdiscovery to inspect supported toolkits and active connection status; inspect the complete selected-tool schema before any live check. - Map active connections to relevant capability categories. Ask only when multiple tools could fill the same category or the mapping is unclear.
- Show the exact proposed connector-map diff based on verified active connections or explicit user choices. Preserve unrelated mappings.
- Immediately before creating or updating
~/.pipa/CONNECTORS.md, require explicit approval for that exact diff. Connector-map write approval is separate from authorization-link completion; never infer one from the other. - Apply only the approved diff, verify the file write, and report success or failure. If the write fails, do not claim the map was updated.
- Never store credentials, authorization links, secrets, or connection status. Check Composio before claiming a mapped tool is active.
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.
- 12d ago First seen · 98 lines · 35 tokens per session scan A a67bae411cbd
pipa-connectors is a skill published in the GitHub repository lunchpaillola/pipa-skills (3 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 1,416 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
autoresearch
Autonomously optimize any Claude Code skill by running it repeatedly, scoring outputs against binary evals, mutating the prompt, and keeping improvements. Based on Karpathy's autoresearch methodology. Use when: optimize this skill, improve this skill, run autoresearch on, make this skill better, self-improve skill…
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
json-canvas
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
obsidian-markdown
Create and edit Obsidian Flavored Markdown with wikilinks, embeds, callouts, properties, and other Obsidian-specific syntax. Use when working with .md files in Obsidian, or when the user mentions wikilinks, callouts, frontmatter, tags, embeds, or Obsidian notes.
compound
Capture and compound learnings from conversations into reusable commands and skills through interactive dialogue.
obsidian-cli
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their…