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 historygit 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/history)<a href="https://agentmods.dev/skills/hmbown/wizards-of-the-ghosts/history"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/history/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/history"><img src="https://agentmods.dev/badge/skills/hmbown/wizards-of-the-ghosts/history.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.00074 | $0.00703 |
| Opus 5 | $0.00037 | $0.00351 |
| Sonnet 5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00007 | $0.00070 |
Grade A, and why
history 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.
History
Trace how a system, decision, or codebase arrived at its current state.
What This Skill Does
In D&D, History recalls significant past events, legendary figures, and ancient knowledge. The real-world version is temporal investigation: git blame across the entire project, reading changelogs to understand why a decision was made, reconstructing the sequence of events that led to a production incident, or understanding organizational context that explains why the code looks the way it does. In this grimoire, History is treated as a metaphorical skill with a shipping-now delivery profile. Canonical reference input: History (skill).
When To Use
- You need to understand why something is the way it is — not just what it does, but how it got here.
- A post-mortem or root-cause analysis needs the timeline of events reconstructed.
- Legacy code or legacy decisions need context before you can safely change them.
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 what you need the history of: a codebase, a decision, an incident, or an organizational pattern.
- Reconstruct the timeline: what happened, in what order, and what caused each transition.
- Identify the key decision points: where could things have gone differently, and why did they go this way?
- Deliver the historical narrative with a note on which parts are documented and which are reconstructed.
- Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.
Deliverables
- A timeline of the relevant history: events, decisions, and transitions in order.
- Key decision points identified: what was decided, why, and what the alternatives were.
- Context that explains the current state and constrains future changes.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- History is reconstruction, not certainty. Always note where the record is incomplete or ambiguous.
- Do not assume past decisions were wrong just because the current state is problematic. Context matters.
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 · 74 tokens per session scan A 91ada93e491c
history 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 74 tokens to every session and 703 once invoked, about $0.0004 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
issue-solver
Autonomous engineering agent that reads GitHub issues, traces root causes, designs GRASP-compliant fixes, runs tests, opens PRs, and closes issues only after merge.
refactor-planner
Turn a messy code area into a scoped refactor plan with risk controls.
stale-patch-reconciliation
Use when a patch/diff must be compared with, repaired against, or refreshed for a moving checkout — "is this patch still needed", "does upstream already contain it", "what changed since it was written", "reconcile X.diff with HEAD", or "make apply-patches pass again".
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
caveman-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit.…