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 aAAaqwq/AGI-Super-Team --skill close-automationgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/close-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/close-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/close-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/aaaaqwq/agi-super-team/close-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/close-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01619 |
| Opus 5 | $0.00020 | $0.00809 |
| Sonnet 5 | $0.00008 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
close-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 5d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close CRM Automation via Rube MCP
Automate Close CRM operations through Composio's Close toolkit via Rube MCP.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Close connection via
RUBE_MANAGE_CONNECTIONSwith toolkitclose - 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 toolkitclose - If connection is not ACTIVE, follow the returned auth link to complete Close API authentication
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Leads
When to use: User wants to create new leads or manage existing lead records
Tool sequence:
CLOSE_CREATE_LEAD- Create a new lead in Close [Required]
Key parameters:
name: Lead/company namecontacts: Array of contact objects associated with the leadcustom: Custom field values as key-value pairsstatus_id: Lead status ID
Pitfalls:
- Leads in Close represent companies/organizations, not individual people
- Contacts are nested within leads; create the lead first, then contacts are included
- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names
- Duplicate lead detection is not automatic; check before creating
2. Log Calls
When to use: User wants to log a phone call activity against a lead
Tool sequence:
CLOSE_CREATE_CALL- Log a call activity [Required]
Key parameters:
lead_id: ID of the associated leadcontact_id: ID of the contact calleddirection: 'outbound' or 'inbound'status: Call status ('completed', 'no-answer', 'busy', etc.)duration: Call duration in secondsnote: Call notes
Pitfalls:
- lead_id is required; calls must be associated with a lead
- Duration is in seconds, not minutes
- Call direction affects reporting and analytics
- contact_id is optional but recommended for tracking
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.
- 5d ago First seen · 213 lines · 41 tokens per session scan A 298f9ed5af5e
close-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (91 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,619 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-09-05.
Other skills, from other repositories
spell-schedule
Schedule a moflo spell to run on the local machine via the moflo daemon (cron, interval, or one-time). Use when the user wants to schedule, automate, or recurringly run one of THEIR spells locally — e.g. "schedule the oap spell every hour", "run my audit spell every weekday at 9am", "fire X once tomorrow morning".…
review-deep
Drive the deep-review phase of an automated PR review. Consumes the walkthrough, runs the deterministic deep-review workflow (parallel lenses → adversarial validation → code-enforced threshold/caps), drafts the surviving findings, and completes the review run.
implement
Implement a Jira ticket — fetches ticket, checks for existing plan, creates worktree branch, runs implementation with verification. Usage - /implement IN-XXX.
plan-week
Weekly planning session — AI interviews you about goals, breaks them into Jira tickets with lightweight plans, creates them after approval. Use when starting the week or planning a batch of work.
plan
Deep planning for a specific Jira ticket — codebase deep-dive, interview on ambiguous points, update ticket with detailed approach. Use before implementing large or unclear tickets. Usage - /plan IN-XXX.
update-task-status
Use when you want to update the workflow status of an octomux task, add a note, rename it, or link external references (e.g. Jira tickets).