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 maystudios/claude-skills --skill hermes-tweetgit clone --depth 1 https://github.com/maystudios/claude-skillsWrote 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/maystudios/claude-skills/hermes-tweet)<a href="https://agentmods.dev/skills/maystudios/claude-skills/hermes-tweet"><img src="https://agentmods.dev/badge/skills/maystudios/claude-skills/hermes-tweet/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/maystudios/claude-skills/hermes-tweet"><img src="https://agentmods.dev/badge/skills/maystudios/claude-skills/hermes-tweet.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.00050 | $0.00436 |
| Opus 5.5 | $0.00020 | $0.00174 |
| Sonnet 5.5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
hermes-tweet 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 2mo 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
Hermes Tweet
Hermes Tweet is a Hermes Agent plugin for X/Twitter workflows. It keeps endpoint discovery separate from reads and requires explicit configuration before account data or publishing actions are available.
Install
hermes plugins install Xquik-dev/hermes-tweet --enable
Set XQUIK_API_KEY before using read or action tools. Set
HERMES_TWEET_ENABLE_ACTIONS=true only for projects where publishing actions
are intentionally enabled.
Tool Routes
tweet_explore: discover the bundled X/Twitter endpoint catalog without network access.tweet_read: read public, read-only X/Twitter data from a cataloged GET endpoint whenXQUIK_API_KEYis configured.tweet_action: run private or action-marked GET endpoints, draft, schedule, or publish only whenXQUIK_API_KEYis configured andHERMES_TWEET_ENABLE_ACTIONS=true.
Workflow
- Use
tweet_exploreto find the endpoint that matches the user's request. - Use
tweet_readfor public timelines, profile reads, search, or analytics. - Use
tweet_actionfor connected-account state, private GET endpoints, action-marked endpoints, or publishing after clear user approval. - Report what was read or drafted without exposing private account state.
Safety
- Keep all publishing actions explicit and reviewable.
- Treat private account state as sensitive context.
- Do not enable
tweet_actionfor unattended projects. - Do not store API keys, account data, or drafts in the repository.
Links
- Plugin: https://github.com/Xquik-dev/hermes-tweet
- Hermes Agent: https://github.com/NousResearch/hermes-agent
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.
- 2mo ago First seen · 54 lines · 50 tokens per session scan A 9eb86d550470
hermes-tweet is a skill published in the GitHub repository maystudios/claude-skills (26 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 436 once invoked, about $0.0002 per session on Opus 5.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
timescaledb-hyperfunctions
Use this skill when writing analytical SQL over time-series data with the TimescaleDB Toolkit (timescaledbtoolkit extension) hyperfunctions: approximate percentiles, statistical summaries, time-weighted averages, counter/gauge rates, uptime/heartbeat tracking, state durations, OHLC candlesticks, approximate distinct…
pgvector-semantic-search
Use this skill for setting up vector similarity search with pgvector for AI/ML embeddings, RAG applications, or semantic search. Trigger when user asks to: Store or search vector embeddings in PostgreSQL Set up semantic search, similarity search, or nearest neighbor search Create HNSW or IVFFlat indexes for vectors…
postgres
Use this skill for any PostgreSQL database work — table design, indexing, data types, constraints, extensions (pgvector, PostGIS, TimescaleDB), search, and migrations. Trigger when user asks to: Explore an existing PostgreSQL database to understand its objects and relationships Design or modify PostgreSQL tables…
cloudflare-development
Cloudflare Workers, Pages, KV, D1, R2, and Durable Objects development best practices for edge computing applications.
grpc-development
Best practices for building high-performance services with gRPC and Protocol Buffers. Use when designing RPC services, defining protobuf schemas, implementing streaming APIs, setting up gRPC interceptors, or building cross-language service communication.
kafka-development
Best practices for Apache Kafka event streaming and distributed messaging. Use when building event-driven architectures, implementing producer/consumer patterns, designing topic partitioning strategies, setting up Kafka Streams, configuring schema registries, or integrating change data capture pipelines.