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 nevergoodstudy-hub/wechat-article-summarizer --skill capsule_crm-automationgit clone --depth 1 https://github.com/nevergoodstudy-hub/wechat-article-summarizerWrote 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/nevergoodstudy-hub/wechat-article-summarizer/capsule_crm-automation)<a href="https://agentmods.dev/skills/nevergoodstudy-hub/wechat-article-summarizer/capsule_crm-automation"><img src="https://agentmods.dev/badge/skills/nevergoodstudy-hub/wechat-article-summarizer/capsule_crm-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.
<a href="https://agentmods.dev/skills/nevergoodstudy-hub/wechat-article-summarizer/capsule_crm-automation"><img src="https://agentmods.dev/badge/skills/nevergoodstudy-hub/wechat-article-summarizer/capsule_crm-automation.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.00041 | $0.00970 |
| Opus 5 | $0.00020 | $0.00485 |
| Sonnet 5 | $0.00008 | $0.00194 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
capsule_crm-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 7d 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 capsule_crm-automation — 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capsule CRM Automation via Rube MCP
Automate Capsule CRM operations through Composio's Capsule CRM toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/capsule_crm
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Capsule CRM connection via
RUBE_MANAGE_CONNECTIONSwith toolkitcapsule_crm - Always call
RUBE_SEARCH_TOOLSfirst 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.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitcapsule_crm - If connection is not ACTIVE, follow the returned auth link to complete setup
- Confirm connection status shows ACTIVE before running any workflows
Tool Discovery
Always discover available tools before executing workflows:
RUBE_SEARCH_TOOLS: queries=[{"use_case": "contacts, opportunities, cases, tasks, and pipeline management", "known_fields": ""}]
This returns:
- Available tool slugs for Capsule CRM
- Recommended execution plan steps
- Known pitfalls and edge cases
- Input schemas for each tool
Core Workflows
1. Discover Available Capsule CRM Tools
RUBE_SEARCH_TOOLS:
queries:
- use_case: "list all available Capsule CRM tools and capabilities"
Review the returned tools, their descriptions, and input schemas before proceeding.
2. Execute Capsule CRM Operations
After discovering tools, execute them via:
RUBE_MULTI_EXECUTE_TOOL:
tools:
- tool_slug: "<discovered_tool_slug>"
arguments: {<schema-compliant arguments>}
memory: {}
sync_response_to_workbench: false
3. Multi-Step Workflows
For complex workflows involving multiple Capsule CRM operations:
- Search for all relevant tools:
RUBE_SEARCH_TOOLSwith specific use case - Execute prerequisite steps first (e.g., fetch before update)
- Pass data between steps using tool responses
- Use
RUBE_REMOTE_WORKBENCHfor bulk operations or data processing
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.
- 7d ago First seen · 111 lines · 41 tokens per session scan A ed3842ac9cbb
capsule_crm-automation is a skill published in the GitHub repository nevergoodstudy-hub/wechat-article-summarizer (5 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 970 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to capsule_crm-automation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery.
tasks
Create or update the live task dashboard (TASKS.md) in Obsidian. Use when the user wants to view or regenerate the task dashboard — 'show my tasks', 'update TASKS.md', 'open task view'. Do NOT use for: the vault portal/map (use moc), capturing new tasks (add them inside project notes directly), or daily briefing (use…
ariadne:workstream-tracking
Create, audit, or improve Obsidian Kanban work boards and Dataview dashboards for durable project, roadmap, evaluation, implementation, QA, or recurring workstream tracking inside an agent-maintained vault.
notion-docs
Notion workspace management via MCP - create databases, pages, comments, and knowledge bases. Use when building Notion documentation, organizing project wikis, or managing Notion content.