Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/commands/ketankhairnar/ai-sales-team-public/xresearch)<a href="https://agentmods.dev/commands/ketankhairnar/ai-sales-team-public/xresearch"><img src="https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/xresearch/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/commands/ketankhairnar/ai-sales-team-public/xresearch"><img src="https://agentmods.dev/badge/commands/ketankhairnar/ai-sales-team-public/xresearch.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.00032 | $0.02856 |
| Opus 5 | $0.00016 | $0.01428 |
| Sonnet 5 | $0.00006 | $0.00571 |
| Haiku 4.5 | $0.00003 | $0.00286 |
Grade A, and why
xresearch 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 12d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xresearch — Twitter/X Profile Intelligence
Step 1: Parse & Setup
- Extract the handle from
$ARGUMENTS(strip@if present, strip whitespace). - Create a slug from the handle (lowercase, as-is). Example:
trading_wise→trading_wise. - Set paths:
PROSPECT_DIR=prospects/{slug}/RAW_DATA=prospects/{slug}/twitter_raw_data.jsonOUTPUT=prospects/{slug}/notes/xresearcher-intake.mdCOOKIES=plugins/xresearch/.cookies.jsonSCRAPER=plugins/xresearch/xresearch.py
- Create directories:
prospects/{slug}/notes/(usemkdir -p).
IMPORTANT: Before running the scraper, check if twitter_raw_data.json already exists at the output path. Also check for legacy raw_data.json (older runs). If either exists, ask the user:
"twitter_raw_data.json (or raw_data.json) already exists for {handle}. Use existing data or re-scrape?" If they say use existing, skip Step 2 entirely. If using legacy
raw_data.json, setRAW_DATAto that path.
Step 2: Run Scraper
Run the Playwright scraper via Bash:
cd /Users/ketankhairnar/Desktop/AIC && python plugins/xresearch/xresearch.py {handle} {RAW_DATA} --cookies {COOKIES}
- If exit code != 0, show the error and STOP. Do not proceed with stale or missing data.
- If successful, read
twitter_raw_data.jsonand report:
✓ Scraper complete
Tweets: {meta.tweet_count_collected} ({meta.date_range[0]} to {meta.date_range[1]})
Following: {meta.following_collected}/{meta.following_total}
Links: {links count} extracted, {scraped_links count} scraped
Status: {scrape_status summary}
Step 3: Read Raw Data
Read the full twitter_raw_data.json into context. You need ALL of it for the analysis passes.
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.
- 12d ago First seen · 308 lines · 32 tokens per session scan A d648e4ed3ac6
xresearch is a command published in the GitHub repository ketankhairnar/ai-sales-team-public (2 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 2,856 once invoked, about $0.0002 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 commands, from other repositories
bulk
Batch API processing with 50% cost savings.
help
Quick reference for all Attune commands.
spec
Spec-driven development — brainstorm, plan, review, and execute with quality gates and approval.
analyze
Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities.
doc-gen
Generate documentation from source code — docstrings, README sections, API references.
fix-test
Auto-diagnose and fix failing tests — identifies root causes and applies fixes.