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 manu14357/zskills --skill anthropic_administrator-automationgit clone --depth 1 https://github.com/manu14357/zskillsWrote 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/manu14357/zskills/anthropic_administrator-automation)<a href="https://agentmods.dev/skills/manu14357/zskills/anthropic_administrator-automation"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/anthropic_administrator-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/manu14357/zskills/anthropic_administrator-automation"><img src="https://agentmods.dev/badge/skills/manu14357/zskills/anthropic_administrator-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.00983 |
| Opus 5 | $0.00021 | $0.00491 |
| Sonnet 5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
anthropic_administrator-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 9d 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 anthropic_administrator-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.
Anthropic Admin Automation via Rube MCP
Automate Anthropic Admin operations through Composio's Anthropic Admin toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/anthropic_administrator
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Anthropic Admin connection via
RUBE_MANAGE_CONNECTIONSwith toolkitanthropic_administrator - 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 toolkitanthropic_administrator - 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": "API keys, usage, workspaces, and organization management", "known_fields": ""}]
This returns:
- Available tool slugs for Anthropic Admin
- Recommended execution plan steps
- Known pitfalls and edge cases
- Input schemas for each tool
Core Workflows
1. Discover Available Anthropic Admin Tools
RUBE_SEARCH_TOOLS:
queries:
- use_case: "list all available Anthropic Admin tools and capabilities"
Review the returned tools, their descriptions, and input schemas before proceeding.
2. Execute Anthropic Admin 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 Anthropic Admin 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.
- 9d ago First seen · 111 lines · 42 tokens per session scan A 8ed966b81c33
anthropic_administrator-automation is a skill published in the GitHub repository manu14357/zskills (16 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 983 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 anthropic_administrator-automation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…