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 Hmbown/Wizards-of-the-Ghosts --skill glibnessgit clone --depth 1 https://github.com/Hmbown/Wizards-of-the-GhostsWrote 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/hmbown/wizards-of-the-ghosts/glibness)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/glibness"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/glibness/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/hmbown/wizards-of-the-ghosts/glibness"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/glibness.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.00062 | $0.00659 |
| Opus 5 | $0.00031 | $0.00329 |
| Sonnet 5 | $0.00012 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
glibness 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 9d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Glibness
Make any argument sound maximally credible and polished.
What This Skill Does
Glibness makes everything you say sound utterly convincing. The real-world version is rhetorical polish: taking a position and presenting it with maximum confidence, fluency, and persuasive structure. This is the skill of the trial lawyer, the pitch artist, the keynote speaker who makes mediocre ideas sound inevitable. In this grimoire, Glibness is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: Glibness (spell).
When To Use
- You have a position that is substantively sound but needs to be presented with maximum rhetorical force.
- A pitch, proposal, or argument needs polish to match the quality of its underlying logic.
- You want to rehearse or draft language that sounds confident and authoritative.
Prerequisites
- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.
Procedure
- Restate the target, the success condition, and any no-touch boundaries before taking action.
- Identify the core argument and its strongest supporting evidence.
- Strip hedging language, unnecessary qualifiers, and weak framing.
- Restructure for maximum impact: lead with the conclusion, back with evidence, close with the ask.
- Audit for dishonesty: flag anywhere the polish is masking a genuine weakness rather than presenting a genuine strength.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A polished version of the argument with confident, authoritative language.
- A honesty audit: notes on where rhetorical polish is covering real weaknesses.
- Alternative framings ranked by persuasive force.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Flag when polish is compensating for a fundamentally flawed argument. Glibness should amplify truth, not manufacture it.
- Distinguish between legitimate confidence and dishonest certainty. Saying something confidently does not make it true.
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.
- 9d ago First seen · 67 lines · 62 tokens per session scan A f5c93e30ee22
glibness is a skill published in the GitHub repository Hmbown/Wizards-of-the-Ghosts (107 stars, last pushed 5mo ago), licensed CC0-1.0. It adds 62 tokens to every session and 659 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
agent-creator
Meta-agent for creating new custom agents, skills, and MCP integrations. Expert in agent design, MCP development, skill architecture, and rapid prototyping. Activate on 'create agent', 'new skill', 'MCP server', 'custom tool', 'agent design'. NOT for using existing agents (invoke them directly), general coding (use…
code-research
Use when produce structured understanding of unfamiliar codebases — architecture, data flows, dependencies, and conventions. Use when joining a new project, tracing feature implementations, or mapping system architecture.
crewai-agents
Use when crewAI multi-agent orchestration — agents, tasks, crews, tools, memory, delegation. Use when working with crewai agents.
code-agent
Use when implementing features from specs — reads requirements, writes code with tests, iterates until verification passes.
deploy-agent
Use when ship code through controlled pipeline with verification gates and rollback plans.
planning-agent
Use when decompose complex tasks into executable steps with dependencies, risk assessment, and verification criteria.