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/unifapi-agent/agents/threadsnpx skills add unifapi-agent/agents --skill threadsgit clone --depth 1 https://github.com/unifapi-agent/agentsWhat 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 | $0.00101 | $0.01317 |
| Opus 5 | $0.00051 | $0.00659 |
| Sonnet 5 | $0.00020 | $0.00263 |
| Haiku 4.5 | $0.00010 | $0.00132 |
Grade A, and why
threads 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
threads
The deterministic read path for public Threads (Meta) data through UnifAPI.
This is a Data Skill: it does not run a marketing job on its own — it names
the concrete threads/... operations, response shapes, and gotchas so any
text-first listening or content workflow reads from one known recipe instead of
rediscovering the surface each time.
Read-only — eyes, not hands. It researches public Threads data and returns cited records; it never posts or replies, and UnifAPI never holds Threads credentials.
Use the unifapi skill for live evidence
Connect once through the shared unifapi skill (OAuth MCP), then call the
operations below. Profiles are keyed by {username}. Keep any billing
metadata so the output can state record cost.
Response contract
Single-entity endpoints return the object in data:
{
"request_id": "unif_...",
"data": {},
"billing": { "records_charged": 1, "balance_remaining": 99 }
}
List endpoints return an array in data plus pagination:
{
"request_id": "unif_...",
"data": [],
"pagination": { "has_more": false, "next_cursor": null },
"billing": { "records_charged": 1 }
}
When pagination.has_more is true, pass pagination.next_cursor as the next
request's cursor. Always preserve billing when reporting cost.
Core operations
| Need | Operation |
|---|---|
| Newest posts on a term | threads/search/recent (?q=...) |
| Most-seen posts on a term | threads/search/top (?q=...) |
| Profiles on a term | threads/search/profiles (?q=...) |
| Profile by handle | threads/users/{username} |
| A handle's posts | threads/users/{username}/posts |
| A handle's replies | threads/users/{username}/replies |
| A handle's reposts | threads/users/{username}/reposts |
Need a field not listed here? Use the unifapi skill's get_operation to read
the exact schema before calling — but pick the operation from this table, don't
discover blind.
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.
- 2d ago First seen · 122 lines · 101 tokens per session scan A 69136e0b126b
threads is a skill published in the GitHub repository unifapi-agent/agents (557 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 1,317 once invoked, about $0.0005 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-30.
Other skills, from other repositories
orangeo-ai-visibility-skill
Audit brand AI visibility readiness and prepare OranGEO-style GEO, AEO, LLM SEO, and AI search optimization action plans. Use when asked for a Claude Code skill, Codex skill, GEO skill, generative engine optimization skill, answer engine optimization skill, AI visibility audit, AI search visibility checker, llms.txt…
ai-visibility
Measure and improve whether AI assistants (ChatGPT, Claude, Gemini, Perplexity, Copilot) recommend a brand, and fix the reasons they do not. Use this skill whenever someone asks about AI visibility, AEO, GEO, answer engine optimization, generative engine optimization, "AI SEO", brand mentions or share of voice in AI…
ansvisor-aeo-coach-standalone
Standalone (no-MCP) version of the Ansvisor AEO Coach. Use this only when the user's Claude client cannot connect to the Ansvisor MCP server (e.g. claude.ai web without a Connector configured). Fetches live data from the Ansvisor REST API directly with the user's API key via code execution. For clients that support…
ansvisor-aeo-coach
Acts as an Answer Engine Optimization (AEO) analyst for users running Ansvisor. Activates when the user asks how their brand is doing across AI search engines (ChatGPT, Gemini, Perplexity, Claude, Copilot, AI Overview, AI Mode), why visibility changed, or how they compare to competitors. Uses the Ansvisor MCP server…
open-geo
Run an end-to-end GEO visibility measurement through a real AI interface, persist the captures, and return a portable JSON run artifact plus optional PDF/dashboard outputs. Use automatically on an explicit request to measure a brand's AI-search visibility, and as a composable data-collection step inside another agent…
geo-platform-optimizer
Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually.