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 box-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/box-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/box-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/box-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/box-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/box-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.00044 | $0.02996 |
| Opus 5 | $0.00022 | $0.01498 |
| Sonnet 5 | $0.00009 | $0.00599 |
| Haiku 4.5 | $0.00004 | $0.00300 |
Grade A, and why
box-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
91% identical to box-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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Box Automation via Rube MCP
Automate Box operations including file upload/download, content search, folder management, collaboration, metadata queries, and sign requests through Composio's Box toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Box connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbox - 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 toolkitbox - If connection is not ACTIVE, follow the returned auth link to complete Box OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Upload and Download Files
When to use: User wants to upload files to Box or download files from it
Tool sequence:
BOX_SEARCH_FOR_CONTENT- Find the target folder if path is unknown [Prerequisite]BOX_GET_FOLDER_INFORMATION- Verify folder exists and get folder_id [Prerequisite]BOX_LIST_ITEMS_IN_FOLDER- Browse folder contents and discover file IDs [Optional]BOX_UPLOAD_FILE- Upload a file to a specific folder [Required for upload]BOX_DOWNLOAD_FILE- Download a file by file_id [Required for download]BOX_CREATE_ZIP_DOWNLOAD- Bundle multiple files/folders into a zip [Optional]
Key parameters:
parent_id: Folder ID for upload destination (use"0"for root folder)file: FileUploadable object withs3key,mimetype, andnamefor uploadsfile_id: Unique file identifier for downloadsversion: Optional file version ID for downloading specific versionsfields: Comma-separated list of attributes to return
Pitfalls:
- Uploading to a folder with existing filenames can trigger conflict behavior; decide overwrite vs rename semantics
- Files over 50MB should use chunk upload APIs (not available via standard tools)
- The
attributespart of upload must come before thefilepart or you get HTTP 400 withmetadata_after_file_contents - File IDs and folder IDs are numeric strings extractable from Box web app URLs (e.g.,
https://*.app.box.com/files/123gives file_id"123")
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 · 234 lines · 44 tokens per session scan A 510d2e714b34
box-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (92 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,996 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to box-automation, differing in 7 lines, and is treated as a copy.
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).