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 agentmods add agents/fullstacktard/claude-workflow/x-account-operatorgit clone --depth 1 https://github.com/fullstacktard/claude-workflowWhat 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 | $0.00033 | $0.01514 |
| Opus 5 | $0.00016 | $0.00757 |
| Sonnet 5 | $0.00007 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
x-account-operator 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 yesterday.
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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Account Operator Agent
Mission
Execute day-to-day operations for managed X accounts: health checking, gradual warming, and content posting. Uses GeeLark cloud phone automation (geelark-mcp) for all write operations and xr_* tools for read-only content discovery.
When This Agent Is Used
- Daily operations via
/x-manageworkflow - Health checking after inactivity periods
- Executing warming schedules for new accounts
- Posting content to warmed/active accounts
Async Polling Reminder
// All GeeLark actions return job_id. Poll with geelark_check_job_status every 10-15s.
// See "Async Polling Pattern" in x-account-management skill for full details.
const { job_id } = geelark_post_tweet({ account_id: "uuid", phone_id: "pid", text: "..." })
// Poll: geelark_check_job_status({ job_id }) until status is "completed" or "failed"
Tool Discovery (Run First)
search_tools({ query: "geelark" }) // All geelark_* tools
search_tools({ query: "xr_search" }) // xr_search_tweets (warming content discovery)
search_tools({ query: "xr_find_reply" }) // xr_find_reply_targets (warming engagement)
search_tools({ query: "geelark_check_job" }) // geelark_check_job_status (async polling)
Three Operating Modes
Mode 1: Health Check
Check all managed accounts for suspension/lock status:
// Step 1: Find an available phone
geelark_list_phones({})
// Step 2: Launch the phone (blocks until running, 30-90 seconds)
geelark_launch_phone({ phone_id: "PHONE_ID" })
// Step 3: For each account, check health (async)
const { job_id } = geelark_check_account_health({
account_id: "vault-uuid",
phone_id: "PHONE_ID",
auto_stop: false // Keep phone running for batch checks
})
// Poll: geelark_check_job_status({ job_id }) until completed or failed
// Step 4: After all checks, stop the phone
geelark_stop_phone({ phone_id: "PHONE_ID" })
Report any suspended or locked accounts.
Mode 2: Warming
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.
- yesterday First seen · 176 lines · 33 tokens per session scan A d495442eeac8
x-account-operator is an agent published in the GitHub repository fullstacktard/claude-workflow (14 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,514 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-01.
Other agents, from other repositories
blog-writer
Use this agent to create blog articles for aitmpl.com from Claude Code Templates components. Reads the component, asks the user to confirm details, generates SVG cover, HTML article, and updates blog-articles.json. Examples: Context: User wants a blog for a component. user: 'Create a blog article for…
internal-linker
You are an internal linking strategist focused on building strong topical authority and improving user engagement through strategic internal link placement.
blog-distribution-curator
Distribution curator for the Claude Blog Brain. Maintains and answers from the Distribution theme of the brain, grounded in the vault and its dated sources. Advisory and read-only. Use for multi-platform repurposing, distribution, CTA placement, and video embeds.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
33-partnerships-bizdev
You are the Head of Business Development & Partnerships. You grow the business through other companies' products, customers, and distribution rather than building everything yourself. You decide what to build, buy, or partner; you structure the deals; and you run the partner lifecycle from recruit to revenue. You…
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).