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 basecamp-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/basecamp-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/basecamp-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/basecamp-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/basecamp-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/basecamp-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.00042 | $0.03243 |
| Opus 5 | $0.00021 | $0.01622 |
| Sonnet 5 | $0.00008 | $0.00649 |
| Haiku 4.5 | $0.00004 | $0.00324 |
Grade A, and why
basecamp-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
98% identical to basecamp-automation — 7 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Basecamp Automation via Rube MCP
Automate Basecamp operations including project management, to-do list creation, task management, message board posting, people management, and to-do group organization through Composio's Basecamp toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Basecamp connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbasecamp - 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 toolkitbasecamp - If connection is not ACTIVE, follow the returned auth link to complete Basecamp OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage To-Do Lists and Tasks
When to use: User wants to create to-do lists, add tasks, or organize work within a Basecamp project
Tool sequence:
BASECAMP_GET_PROJECTS- List projects to find the target bucket_id [Prerequisite]BASECAMP_GET_BUCKETS_TODOSETS- Get the to-do set within a project [Prerequisite]BASECAMP_GET_BUCKETS_TODOSETS_TODOLISTS- List existing to-do lists to avoid duplicates [Optional]BASECAMP_POST_BUCKETS_TODOSETS_TODOLISTS- Create a new to-do list in a to-do set [Required for list creation]BASECAMP_GET_BUCKETS_TODOLISTS- Get details of a specific to-do list [Optional]BASECAMP_POST_BUCKETS_TODOLISTS_TODOS- Create a to-do item in a to-do list [Required for task creation]BASECAMP_CREATE_TODO- Alternative tool for creating individual to-dos [Alternative]BASECAMP_GET_BUCKETS_TODOLISTS_TODOS- List to-dos within a to-do list [Optional]
Key parameters for creating to-do lists:
bucket_id: Integer project/bucket ID (from GET_PROJECTS)todoset_id: Integer to-do set ID (from GET_BUCKETS_TODOSETS)name: Title of the to-do list (required)description: HTML-formatted description (supports Rich text)
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 · 235 lines · 42 tokens per session scan A dda23dc503c2
basecamp-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (92 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 3,243 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to basecamp-automation, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
flo
MoFlo ticket spell - analyze and execute GitHub issues.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.