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 fullstacktard/claude-workflow --skill x-persona-managementgit 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/skills/fullstacktard/claude-workflow/x-persona-management)<a href="https://agentmods.dev/skills/fullstacktard/claude-workflow/x-persona-management"><img src="https://agentmods.dev/badge/skills/fullstacktard/claude-workflow/x-persona-management/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/fullstacktard/claude-workflow/x-persona-management"><img src="https://agentmods.dev/badge/skills/fullstacktard/claude-workflow/x-persona-management.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.00054 | $0.02973 |
| Opus 5.5 | $0.00022 | $0.01189 |
| Sonnet 5.5 | $0.00011 | $0.00595 |
| Haiku 4.5 | $0.00005 | $0.00297 |
Grade A, and why
x-persona-management 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 — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Persona & Feed Management Skill
Manage the full persona-to-publication pipeline: create personas, configure feeds, generate content, review drafts, and publish via GeeLark.
When to Use This Skill
- Creating or editing X personas (character definitions, voice, topics)
- Configuring feed monitoring (watched accounts, subjects, trending)
- Setting up content generation schedules
- Reviewing, approving, or rejecting generated drafts
- Publishing approved content to X via GeeLark
- Configuring agent settings (model, max turns)
Tool Discovery (Run First)
search_tools({ query: "xp_" }) // All 34 x-persona tools
search_tools({ query: "geelark_post" }) // Publishing tools
search_tools({ query: "vault_" }) // Account vault tools
Core Concepts
Persona
An ElizaOS-compatible character definition with name, bio, topics, style, and optional agent settings. Personas generate content independently -- they do NOT require a linked Twitter account.
Feed Config
One-to-one with a persona. Controls monitoring intervals, daily generation limits, and Telegram notifications. Has child entities: watched accounts, subjects, schedules.
Draft Lifecycle
generated → approved → published
↘ rejected
Persona Management
Create a Persona
xp_create_persona({
character: {
name: "CryptoAnalyst",
bio: "On-chain analyst tracking DeFi protocols and market structure. Data-driven, contrarian, concise.",
username: "cryptoanalyst",
topics: ["defi", "on-chain analytics", "market structure"],
adjectives: ["analytical", "concise", "contrarian", "data-driven"],
postExamples: [
"TVL doesn't lie. Three protocols just crossed $1B with zero token incentives. That's real demand.",
"Everyone's watching price. Nobody's watching the funding rate divergence. This happened twice before — both times preceded 30%+ moves."
],
style: {
all: ["Use data and metrics to support claims", "Be concise — tweets under 200 chars preferred"],
post: ["No hashtags", "No emojis", "Thread for complex analysis"],
reply: ["Be conversational", "Reference the original tweet's key point"],
quote_tweet: ["Add original insight, don't just agree"],
article: ["Use headers and data tables", "Cite sources"],
long_form: ["Build a narrative arc", "End with actionable takeaway"]
},
settings: {
model: "claude-sonnet-4-6", // or claude-opus-4-6, claude-haiku-4-5-20251001
maxTurns: 10, // Agent research turns (1-50)
mcpServers: { // Per-persona MCP servers (optional)
"signal8": {
type: "stdio",
command: "node",
args: ["/path/to/sec-saas/packages/mcp-server/dist/stdio.js"],
env: { "SIGNAL8_API_KEY": "sk_live_xxx" }
}
}
}
},
account_ids: [] // Optional: link vault account IDs for publishing
})
// Returns: { id: "uuid", name: "CryptoAnalyst", ... }
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 · 418 lines · 54 tokens per session scan A be50756481c3
x-persona-management is a skill published in the GitHub repository fullstacktard/claude-workflow (12 stars, last pushed 6mo ago), licensed MIT. It adds 54 tokens to every session and 2,973 once invoked, about $0.0002 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 skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…