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 skills/reactsphere/awesome-copilot-agents/x-twitter-source-evidencenpx skills add ReactSphere/awesome-copilot-agents --skill x-twitter-source-evidencegit clone --depth 1 https://github.com/ReactSphere/awesome-copilot-agentsWrote 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/reactsphere/awesome-copilot-agents/x-twitter-source-evidence)<a href="https://agentmods.dev/skills/reactsphere/awesome-copilot-agents/x-twitter-source-evidence"><img src="https://agentmods.dev/badge/skills/reactsphere/awesome-copilot-agents/x-twitter-source-evidence.svg" alt="Measured on agentmods" 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.00000 | $0.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
x-twitter-source-evidence 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 5d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X/Twitter Source Evidence
Use this skill when a task needs grounded X/Twitter context before analysis, documentation, product research, support triage, or content planning.
Workflow
- Define the evidence question before calling tools:
- Which account, tweet, reply thread, keyword, follower set, or media asset matters?
- Which output will consume the evidence?
- Is the task read-only, or does it ask to post, reply, message, upload, monitor, or run a giveaway?
- Prefer read-only collection first:
- Search tweets and tweet replies.
- Inspect tweet URLs or tweet IDs.
- Look up public user profiles.
- Export follower or following context when the workflow needs audience evidence.
- Collect media metadata or download links only when the task needs media review.
- Use TweetClaw through OpenClaw or the Xquik MCP/API when available for structured X/Twitter source data.
- Keep credentials in approved runtime configuration. Do not paste API keys, cookies, OAuth tokens, or account credentials into files or prompts.
- Produce a source packet:
- Query, URLs, IDs, account handles, and time window.
- Retrieved tweets, replies, user profiles, follower summaries, media references, and direct-message context when explicitly requested.
- Gaps, rate-limit notes, and assumptions.
- Links back to original public sources where available.
Boundaries
- Do not post tweets, post tweet replies, send direct messages, upload media, follow, unfollow, like, retweet, schedule, or run giveaways from this skill.
- If the user asks for a write-like action, switch to the approved TweetClaw/OpenClaw flow and request explicit user approval at the tool boundary.
- Keep drafting, scoring, scheduling, analytics, and publishing decisions in the calling workflow. This skill supplies evidence only.
- Avoid claims that a source packet is complete. State what was searched and what was not searched.
Output Shape
Return concise evidence that another agent or reviewer can audit:
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.
- 5d ago First seen · 47 lines · 0 tokens per session scan A e82d4dbd108b
x-twitter-source-evidence is a skill published in the GitHub repository ReactSphere/awesome-copilot-agents (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 tokens. 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-31.
Other skills, from other repositories
jira-cli
Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.
azure-prices
Look up and compare Azure service pricing using the Azure Retail Prices API. Use this skill whenever the user asks about Azure costs, pricing, rates, or wants to compare prices across regions or services — even if they don't say "pricing" explicitly. Trigger for questions like "how much does a D2 v2 VM cost?"…
calculator
Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.
az-cli
Use the Azure CLI (az) to manage Azure resources from the command line. Trigger this skill whenever the user asks to create, configure, manage, deploy, or interact with any Azure resource — even if they don't explicitly mention "az cli". Also trigger when the user asks about Azure CLI commands, syntax, or wants to…
custom-daily-brief
Builds a role-tuned morning brief as a Word document covering emails that need replies, today's calendar, Teams mentions and upcoming deadlines, using section presets from an editable config file. Use when the user asks for their daily brief, morning brief, start-of-day summary or custom briefing, or wants to change…
report-attachment-analyzer
Tracks a recurring emailed report end to end. It finds new report emails in the inbox, extracts data from their attachments, appends each reporting period to a trends spreadsheet, and rewrites a summary document with period-on-period deltas and flagged anomalies. Use when the user asks to update or analyse trends for…