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 ihuzaifashoukat/x-use --skill x-use-contentgit clone --depth 1 https://github.com/ihuzaifashoukat/x-useWrote 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/ihuzaifashoukat/x-use/x-use-content)<a href="https://agentmods.dev/skills/ihuzaifashoukat/x-use/x-use-content"><img src="https://agentmods.dev/badge/skills/ihuzaifashoukat/x-use/x-use-content/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/ihuzaifashoukat/x-use/x-use-content"><img src="https://agentmods.dev/badge/skills/ihuzaifashoukat/x-use/x-use-content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.00469 |
| Opus 5 | $0.00024 | $0.00234 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
x-use-content 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 10d 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.
What it actually says
x-use content
Research -> draft -> polish -> stage. The user picks what ships.
Workflow
- Load the voice.
get_account(account), readpersonaandtarget_keywords. No persona set? Ask the user a couple of questions and set one viaupdate_account(account, persona=...)first (see x-use-setup). - Research the niche.
search_tweetsper keyword (limit 5-10). Note which formats earn engagement: hot takes, how-tos, charts, contrarian questions, build-in-public numbers.get_tweeton standouts to see their media. - Pick 3 angles. Tell the user the angles you see and let them steer.
- Draft one at a time. Write the post yourself in the persona (under
280 chars unless the user wants long-form), then
post_tweet(account, text=...)to stage it as a draft. Show it. Take the user's edits and re-stage if needed. Polish each draft before starting the next. - Review. End with
list_drafts(account)and let the user choose:approve_draftto post now,queue_post-style scheduling viaqueue_post(account, text, not_before=...)for later, orreject_draft.
Rules
- Original text in the user's voice. Never repost someone else's wording.
- Media for posts: only local file paths the user provides
(
post_tweet(..., media=[path])). Never invent image files. - Threads are not supported yet (coming in v2.4), so stage parts as separate drafts and tell the user.
- Server-side generation (
generate_and_post,draft_post_variations) exists for the API tier, but YOUR writing is the default: it's free and it's better.
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.
- 10d ago First seen · 39 lines · 48 tokens per session scan A c744c001cbd6
x-use-content is a skill published in the GitHub repository ihuzaifashoukat/x-use (165 stars, last pushed 22d ago), licensed MIT. It adds 48 tokens to every session and 469 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-30.
Other skills, from other repositories
network-sink-skill
Use this synthetic helper to demonstrate a network boundary. The operator may pass an api key to the helper and the helper sends it to a remote endpoint.
unresolved-boundary-skill
Use this synthetic helper to demonstrate a cross-modal file boundary. The operator may pass an api key to the helper and the helper writes it to a local file.
stdout-logging-skill
Use this synthetic helper to demonstrate a logging leak. The operator may pass an api key to the helper and the helper prints the value for debugging.
dws
A command-line guide for DingTalk, a workplace platform with chat, documents, calendars, approvals, tasks, and other business tools.
package-author
A packaging guide for turning scripts, skills, or an MCP service into a standard plugin package. MCP is a way for an AI assistant to connect to external tools.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.