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 anotb/x-signal --skill x-researchgit clone --depth 1 https://github.com/anotb/x-signalWrote 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/anotb/x-signal/x-research)<a href="https://agentmods.dev/skills/anotb/x-signal/x-research"><img src="https://agentmods.dev/badge/skills/anotb/x-signal/x-research/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/anotb/x-signal/x-research"><img src="https://agentmods.dev/badge/skills/anotb/x-signal/x-research.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.00056 | $0.00718 |
| Opus 5 | $0.00028 | $0.00359 |
| Sonnet 5 | $0.00011 | $0.00144 |
| Haiku 4.5 | $0.00006 | $0.00072 |
Grade A, and why
x-research 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.
What it actually says
X research
- Call
x_statusonly when service, sign-in, or rate health is uncertain. - Use
x_search_accountswhen the task needs people, organizations, experts, emerging accounts, or an exact handle. Continue with its returned cursor only when the next account page is useful. - Plan enough distinct post-query angles to answer the actual question. For a broad single topic, usually combine Top and Latest with a few scoped or Media variants in one
x_search. For multiple topics, label each topic and lens in one consolidated call when practical. Choose useful per-leg limits andresponseLimitfrom the requested breadth; do not request 200 by habit or impose an arbitrary global result ceiling. - Let long research run when it is still gathering useful evidence. Poll with
x_get_runusingview: "summary"; pass the returnedrevisionasifRevisionon later polls so unchanged progress stays small. Read full evidence when it changes or completes. If a result isrunningwithretryAt, retain itsrunId, continue independent reasoning, and poll afterretryAt. Do not launch replacement searches or rapid status probes during the backoff window. - Inspect
totalPosts, the evidence-page cursor, per-leg requested/returned counts, continuation availability, query coverage, lenses, authors, clusters, warnings, and failed legs. Usex_get_evidenceto read more already-stored records without touching X. Usex_continue_searchon only consequential thin legs when genuinely new upstream evidence is needed; repeat it if justified. Add a different angle only for a real evidence gap, not as a substitute for either continuation path. - Use
x_get_timelinefor an exact Following, For You, user, bookmarks, list, or community source. Preserve its cursor when another page is useful. Expand consequential posts withx_get_postwhen thread, reply, or quote-post context could confirm, qualify, or challenge the claim. - Synthesize patterns and disagreements across the full evidence set. Distinguish what posts claim, what engagement shows, and what you infer. Canonical X URLs are available when references would improve traceability or the user asks for them. Choose a proportionate set, placement, and style for the specific answer; references may be omitted when they add little value. Do not dump bare URLs or force a fixed citation section unless the user asks.
- Create or change an
x_monitoronly when requested.
Use x_list_runs to find earlier saved research by query, label, status, or creation time. Use x_compare_runs for changes between two saved samples before repeating upstream work. These tools are local. A post absent from the later sample is not evidence of deletion or a decline in discussion. Account, query, lens, and coverage differences matter.
Clusters are lexical groupings of the returned page. Distinct authors or wording do not establish independent corroboration, and translations or synonyms may remain separate. Use explicit recency sorting for chronological historical work; author diversity applies to balanced ranking.
Favor independent coverage and author diversity over volume for its own sake. High engagement is not factual reliability.
What ships with it
1 file 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.
- yesterday Changed · +4 lines 4201b0228fc2
- 12d ago First seen · 18 lines · 56 tokens per session scan A 030906ec7aff
x-research is a skill published in the GitHub repository anotb/x-signal (1 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 718 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
auto-research
Research uncertain questions with an explicit, user-approved web search or ChatGPT consultation, then present options and wait for implementation approval.
odoo-agency-fleet-review
Review many client Odoo databases at once through odoo-mcp's cross-instance tools — fleet-wide accounting health, per-client aging, partial-failure triage — for agencies and partners managing 5–50 instances. Use when the user asks "which client...", "across all instances/databases", or wants a fleet/portfolio status.
odoo-data-quality-gate
Audit an Odoo database's data quality with evidence before trusting AI answers, importing, or migrating — duplicates, missing required values, orphaned references, format anomalies — and drive remediation through odoo-mcp's gated write workflow. Use when the user asks to "check data quality", "clean up data", "prepare…
odoo-migration-copilot
Plan and de-risk an Odoo version upgrade (16→17→18→19/20) using odoo-mcp's migration workbench — audit custom addons, classify upgrade-log failures into a worklist, resolve model renames, and preview JSON-2 payloads for the XML-RPC sunset. Use when the user mentions upgrading/migrating Odoo versions, broken upgrade…
odoo-month-end-close
Drive a month-end accounting close on Odoo through odoo-mcp — AR/AP aging, open-item and draft-invoice review, reconciliation checklists, and chatter documentation — with human sign-off at every posting step. Use when the user asks to "close the month", "review receivables/payables", "check aging", or prepare finance…
add-mechanic
Add game mechanics with correct GDScript 4.x patterns -- movement, health, inventory, save/load.