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 true-strikegit 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/true-strike)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/true-strike"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/true-strike/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/true-strike"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/true-strike.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.00056 | $0.00601 |
| Opus 5 | $0.00028 | $0.00300 |
| Sonnet 5 | $0.00011 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
true-strike 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
True Strike
Aim once with evidence so the next command lands on the first shot.
What This Skill Does
Use this spell for preflight certainty: dry runs, validation checks, dependency verification, and rehearsals that make the next deploy, query, or command much more likely to succeed. It trades a little time up front for fewer blind swings and fewer expensive misses. In this grimoire, True Strike is treated as a metaphorical spell with a shipping-now delivery profile. Canonical reference input: True Strike (spell).
When To Use
- A risky one-shot action should be validated before you fire it.
- A deploy, migration, API call, or command has an expensive miss if it goes wrong.
- You can eliminate common failure modes with a dry run, preflight check, or rehearsal.
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 decisive action and the miss conditions most likely to ruin it.
- Run the smallest useful set of validations or rehearsals that prove readiness.
- Return a go or no-go judgment with the evidence and the uncertainty that remains.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A preflight checklist or dry-run result set.
- A go or no-go recommendation for the next action.
- A short list of residual risks after validation.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not claim certainty when the environment can still change between validation and execution.
- Keep the preflight cheaper than the miss you are trying to avoid.
Verification
- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.
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 · 66 lines · 56 tokens per session scan A 053e167514cc
true-strike 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 56 tokens to every session and 601 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
test-agent
Use when writing comprehensive test suites covering happy paths, error paths, edge cases, and integration points.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
qa-manual-istqb
Create QA artifacts from requirements: test plans, test conditions/cases, bug reports, regression suites, traceability, and exploratory charters. Use for test planning, test design, defects, coverage, or QA deliverables. Applies ISTQB risk-based techniques and loads templates only when needed. Keywords: test plan…
a11y-playwright-testing
Accessibility testing for web applications using Playwright (@playwright/test), TypeScript, and axe-core. Use to write, run, or debug WCAG 2.2 AA checks, keyboard and focus tests, ARIA/semantic validation, accessible names, form labels, color contrast, or screen-reader test patterns. Keywords: accessibility, WCAG…
accessibility-a11y
WCAG 2.2 compliance, ARIA patterns, keyboard navigation, screen readers, automated testing.