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 Gingiris-1031/gingiris-skills --skill gingiris-twitter-agent-opsgit clone --depth 1 https://github.com/Gingiris-1031/gingiris-skillsWrote 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/gingiris-1031/gingiris-skills/gingiris-twitter-agent-ops)<a href="https://agentmods.dev/skills/gingiris-1031/gingiris-skills/gingiris-twitter-agent-ops"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/gingiris-twitter-agent-ops/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/gingiris-1031/gingiris-skills/gingiris-twitter-agent-ops"><img src="https://agentmods.dev/badge/skills/gingiris-1031/gingiris-skills/gingiris-twitter-agent-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 480 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 498 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium MCP Rug Pull · line 686 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00360 | $0.07584 |
| Opus 5.5 | $0.00144 | $0.03034 |
| Sonnet 5.5 | $0.00072 | $0.01517 |
| Haiku 4.5 | $0.00036 | $0.00758 |
Grade A, and why
gingiris-twitter-agent-ops 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 11d 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 — 722 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Twitter/X Agent 运营 SOP v2
版本说明：v2 草稿。v1 给了你整套方法论框架，v2 的重点是： 「已经在跑了，怎么确保不出事、出了事怎么发现、发现了怎么处理」。
⚠️ 开始之前：三个真实事故
在讲 SOP 之前，先讲三个真实踩过的坑。这三件事决定了 v2 的核心设计。
事故 1：cron 超时失败 2 周没人发现
cron job 连续超时失败，没有任何监控机制，整整 2 周没有推文发出。等发现时，粉丝增长已经明显停滞，算法分发也已经冷却。 → v2 修复：强制日报机制，发推后必填，缺了就是异常信号。
事故 2：v0.dev 流量数据相差 17 倍，被用户公开指出
推文中引用了单一数据源（DataForSEO）的「非品牌有机搜索」数字，没有交叉验证，被 @gefei55（哥飞）等用户公开指出数据不准，差了整整 17 倍。 → v2 修复：红线自检中加入「数字来源可查」强制检查项，无来源数字不发。
事故 3：某一话题提及频率过高，被用户指出「天天蹭流量」
某段时期内容过度集中在同一品牌/话题上，用户公开反馈感觉是在持续蹭热度，而不是真正分享。 → v2 修复：任何借势话题每月提及上限 1-2 次，在发推前检查本月该话题已出现次数。
第一步：开局 Context 收集（对话式，必须完成）
Agent 开始运营前，逐步引导用户提供信息，一次只问一个问题。不要一次抛出大表格——用户看到 6 个问题就会不想填。
收集完后给出一段状态判断，再开始工作。
对话引导脚本（按顺序执行）
Q1（先问这个）
你的 Twitter/X 账号是什么？现在有多少粉丝？
→ 记录账号名和粉丝基线，作为后续增长对比
Q2
这个账号主要发什么语言？怎么发推的？
语言（可多选）： A) 中文 B) 英文 C) 中英都有
发布方式： A) 手动发 B) Buffer 排期 C) API 直发（cron 自动） D) 不确定 → 先检查发布机制再继续，cron 挂掉 2 周没人知道是真实事故
→ API 直发：中文账号用 OAuth1 四字段凭证；英文账号用 Buffer channel；两套不能混用
Q3
有素材库吗？
A) 有，大概还有 ___ 条没用（存在：本地文件 / Notion / 飞书 / 其他） B) 有，但不确定有多少 C) 没有
→ A 且条数 ≤ 3：本次先补素材，再排期 → C：第一任务建素材库，今天不开始写推文
Q4
最近发推有记录吗？
A) 有 MASTER-STATUS.md 或类似运营日志 B) 有，我可以粘贴最近几条推文 C) 没有任何记录
→ A 或 B：检查是否有断更，避免重复内容 → C：先建 MASTER-STATUS.md，这是整个系统的单一真相来源
Q5
你现在最想让读者记住你的哪 1-2 件事？受众是什么人？
（自由填写，没有选项——这个要你自己说）
→ 确定内容方向，避免选题漂移
Q6（最后问）
现在最重要的目标是什么？
A) 涨粉 B) 引流到某个链接（是哪个链接？___） C) 建立信任感 / 个人品牌 D) 以上都有，但最重要的是 ___
→ CTA 链接写进每条推文的 reply 策略，不放正文（正文带链接算法惩罚展示量 30-90%）
全部收集后：输出状态判断
📊 当前状态：
- 账号：[@handle]，当前 [X] 粉
- 发布机制：[OAuth1 直发 / Buffer / 手动]
- 素材库：[N] 条可用
- 上周发布：[有记录 / 无记录，需建 MASTER-STATUS.md]
- 内容方向：[用户给的 1-2 件事]
- 本阶段 CTA：[目标 + 链接]
→ 接下来做什么：[3 步以内]
判断矩阵（Agent 内部参考）
| 情况 | 判断 | 处理方式 |
|---|---|---|
| cron 状态不确定 | 🚨 紧急 | 先检查 cron，确认正常再开始内容工作 |
| 素材库 ≤ 3 条 | ⚠️ 预警 | 本次运营优先补充素材库，不排期 |
| 素材库为空 | 🚨 阻塞 | 必须先建素材库才能排期 |
| 上周发布记录缺失 | ⚠️ 提醒 | 让用户打开 MASTER-STATUS.md 核查 |
| MASTER-STATUS.md 不存在 | 🚨 首次运营 | 本次任务先建立 MASTER-STATUS.md |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed · +14 lines 5ea3ddd76190
- 1mo ago First seen · 708 lines · 360 tokens per session scan A 001fe3720eca
gingiris-twitter-agent-ops is a skill published in the GitHub repository Gingiris-1031/gingiris-skills (87 stars, last pushed 11d ago), licensed MIT. It adds 360 tokens to every session and 7,584 once invoked, about $0.0014 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-08-30.
Other skills, from other repositories
zernio
Schedule posts, manage inbox, broadcasts, sequences, and automations across 14 platforms from the CLI.
X Content Advisor
Use when a user asks how to grow or make better content on X/Twitter, wants an account or post audit, asks why a post underperformed, needs a weekly content plan, or wants a draft rewritten, a posting-time experiment, or a recommendation-risk review of sensitive media using evidence from their own timeline. Works with…
social-lead-gen
Lead generation from social media — find high-intent buyers in live Twitter, Instagram, and Reddit conversations. Auto-researches your product, generates targeted search queries, and discovers people actively looking for solutions you offer. Social selling and prospecting powered by billions of indexed posts.
lead-generation
Lead Generation — Find high-intent buyers in live Twitter, Instagram, and Reddit conversations. Auto-researches your product, generates targeted search queries, and discovers people actively looking for solutions you offer. Social selling and prospecting powered by 1.5B+ indexed posts via Xpoz MCP.
viral-x-posts
Write viral X/Twitter posts using 23 proven plug-and-play formulas optimized for the 2025-2026 algorithm. Covers single tweets, threads, engagement bait, and media-enhanced formats. Use when the user asks to: write a tweet, draft an X post, create a thread, write viral content for Twitter/X, craft a hook, create…
twitter-thread-writer
Write X/Twitter threads that get bookmarked, shared, and drive affiliate clicks. Use this skill when the user asks about writing Twitter threads, X threads, tweet threads for affiliate marketing, or says "write a thread about X", "Twitter thread promoting X", "X thread for affiliate", "write tweets that go viral"…