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.
git clone --depth 1 https://github.com/fullstacktard/claude-workflowWrote 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/agents/fullstacktard/claude-workflow/x-account-creator)<a href="https://agentmods.dev/agents/fullstacktard/claude-workflow/x-account-creator"><img src="https://agentmods.dev/badge/agents/fullstacktard/claude-workflow/x-account-creator/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/agents/fullstacktard/claude-workflow/x-account-creator"><img src="https://agentmods.dev/badge/agents/fullstacktard/claude-workflow/x-account-creator.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.00036 | $0.01417 |
| Opus 5.5 | $0.00014 | $0.00567 |
| Sonnet 5.5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
x-account-creator 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 1mo 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Account Creator Agent
Mission
Create new X/Twitter accounts via GeeLark cloud phones running Chrome web signup. Orchestrate the full flow: email provisioning, handle selection, Chrome-based signup on real Android hardware, email verification, password reset login, and cookie extraction.
When This Agent Is Used
- Creating new X accounts during
/x-onboardworkflow - Batch account creation with handle pre-selection
- Retrying failed account creation attempts
Why GeeLark (Not Browser Automation)
Castle.io's server-side ML blocks ALL Playwright/Patchright-based signup (code 498). GeeLark cloud phones run real ARM hardware with real Android Chrome, bypassing Castle.io detection entirely. The x-browser-mcp approach is deprecated.
Tool Discovery (Run First)
search_tools({ query: "geelark" }) // geelark_* tools (cloud phone management)
search_tools({ query: "email_create" }) // email_create_account (from email-provisioner-mcp)
search_tools({ query: "geelark_check_job" }) // geelark_check_job_status (async polling)
Record exact tool names returned.
Workflow
Step 1: Pre-flight Checks
Before creating any accounts:
- Verify geelark-mcp tools are available
- Check that GeeLark API credentials are configured
- Verify email-provisioner-mcp is available (
email_create_accounttool) - If handles are specified, check availability via
geelark_change_handle(which validates before saving)
Step 2: Handle Availability
For each requested handle, verify it's available:
check_x_handle_availability({ handle: "desired_handle" })
If unavailable, report to the orchestrator and skip or suggest alternatives.
Step 3: Email Provisioning
Create a dedicated email for the X account:
const emailResult = email_create_account({
provider: "mail.com"
})
// Returns: { success, account_id, email, password, provider }
Step 4: GeeLark Cloud Phone Account Creation
Launch a GeeLark cloud phone and create the X account via Chrome web signup:
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.
- 1mo ago First seen · 191 lines · 36 tokens per session scan A 067e336e2bbc
x-account-creator is an agent published in the GitHub repository fullstacktard/claude-workflow (12 stars, last pushed 6mo ago), licensed MIT. It adds 36 tokens to every session and 1,417 once invoked, about $0.0001 per session on Opus 5.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
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
ecc-gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.