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 asimons81/hermes-field-kit --skill x-post-writergit clone --depth 1 https://github.com/asimons81/hermes-field-kitWrote 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/asimons81/hermes-field-kit/x-post-writer)<a href="https://agentmods.dev/skills/asimons81/hermes-field-kit/x-post-writer"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/x-post-writer/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/asimons81/hermes-field-kit/x-post-writer"><img src="https://agentmods.dev/badge/skills/asimons81/hermes-field-kit/x-post-writer.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.00046 | $0.02209 |
| Opus 5 | $0.00023 | $0.01104 |
| Sonnet 5 | $0.00009 | $0.00442 |
| Haiku 4.5 | $0.00005 | $0.00221 |
Grade A, and why
x-post-writer 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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
X Post Writer
Overview
Write short-form X content from notes, drafts, links, or verified source material. Default to one finished post unless the user explicitly requests a thread or multiple posts.
Source fidelity outranks punch, post count, inferred benefits, and creative expansion. Internal routing, objectives, verification notes, source ledgers, and quality checks are never part of the delivered copy.
route format -> route source -> choose objective -> verify claims -> draft -> voice pass -> quality gate -> finished text
Load references progressively:
references/formats.mdfor the selected formatreferences/source-routing.mdwhen repurposing or selecting source treatmentreferences/claim-verification.mdfor risky factual claimsreferences/voice-customization.mdwhen a distinct voice must be preservedreferences/algorithm-notes.mdonly for distribution or optimization questions
When to Use
Use this skill for:
- Single X posts, rewrites, launches, link drops, recommendations, or announcements
- Quote posts or commentary on an existing X post
- Replies
- Explicit threads or multi-post sequences
- Personal milestones, reflections, or first-person stories
- Fresh X angles from articles, videos, releases, or project updates
Do not use this skill for:
- Long-form X Articles or essay-length content
- Source extraction, account analytics, or media downloading
- Publishing, scheduling, or browser composition without separate authorization
- Claims that require evidence when no evidence can be obtained
Safety Contract
- Never invent personal experience, product use, opinions, endorsements, or results.
- Never add technical mechanisms, benefits, numbers, or attributions that are not supplied or verified.
- Treat private analytics, revenue, customer data, and unpublished information as sensitive.
- Never publish or schedule automatically.
- Current facts and platform behavior must be verified immediately before use.
- An instruction to state a claim is not evidence for that claim.
What ships with it
11 files 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.
- examples/routing-examples.md 1.3 KB
- README.md 3.7 KB
- references/algorithm-notes.md 1.4 KB
- references/claim-verification.md 2.3 KB
- references/formats.md 2.4 KB
- references/source-routing.md 1.6 KB
- references/voice-customization.md 1.0 KB
- references/x-articles-scope-note.md 423 B
- scripts/validate_bundle.py 3.4 KB runs code
- tests/cases.json 5.0 KB
- tests/test_contract.py 2.7 KB runs code
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 · 242 lines · 46 tokens per session scan A 6155649c91a0
x-post-writer is a skill published in the GitHub repository asimons81/hermes-field-kit (125 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,209 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
implement
Execute approved Hardproof tasks during IMPLEMENT with focused tests, durable task updates, and scope-controlled code changes.
orchestrate
Coordinate an active Hardproof run across discovery, design, planning, implementation, review, verification, delivery, and learning.
deliver
Prepare an inspectable Hardproof delivery during DELIVER with final scope, evidence, risks, rollback, and reproducible reporting.
design
Shape the smallest reversible Hardproof design from discovery evidence during DESIGN, including contracts, failures, and risks.
discover
Inspect a Hardproof run's request, repository, constraints, and unknowns during DISCOVERY before proposing a design.
learn
Close a Hardproof run during LEARN by capturing safe provenance-linked lessons or recording an explicit reason to skip them.