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 agentmods add skills/haroontrailblazer/ghost-font-decoder/ghost-decodenpx skills add haroontrailblazer/ghost-font-decoder --skill ghost-decodegit clone --depth 1 https://github.com/haroontrailblazer/ghost-font-decoderWrote 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/haroontrailblazer/ghost-font-decoder/ghost-decode)<a href="https://agentmods.dev/skills/haroontrailblazer/ghost-font-decoder/ghost-decode"><img src="https://agentmods.dev/badge/skills/haroontrailblazer/ghost-font-decoder/ghost-decode.svg" alt="Measured on agentmods" 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 | $0.00064 | $0.01814 |
| Opus 5 | $0.00032 | $0.00907 |
| Sonnet 5 | $0.00013 | $0.00363 |
| Haiku 4.5 | $0.00006 | $0.00181 |
Grade A, and why
ghost-decode 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 5d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ghost-Font Video Decoder
A ghost-font video hides a message in motion: every frame is noise, but the dots inside the letters move coherently. The decoder below accumulates that motion into two images where the letters appear. Run it once, read the word from the images, and report it. Nothing more.
The whole job — do exactly this
-
Write the program in Decoder (below) to
decode.py, then run it once on the video:pip install --quiet opencv-python-headless numpy python decode.py "<video-path>" out -
View both
out/revealed.png(the clean mask — black background, white letters) andout/revealed_heatmap.png(the raw glowing version). Read the word(s) directly from these images. -
Reply with only this — show both images, then the text:
  Text in the video: **<WORD(S)>**
Trust the images — do NOT over-process
The letters are low-contrast, soft blobs. That is the correct, finished output — read it as-is. The most common failure here is not trusting a perfectly readable reveal and then doing pointless extra work that ends in a hallucinated answer. So:
- Run the decoder once. Do not build a second decoder, try another method (temporal variance, phase correlation, sub-pixel warping, weighted accumulation), or "improve" the approach. One run, then read.
- Produce exactly two images —
revealed.pngandrevealed_heatmap.png. Do not create any other images: no crops, no diagnostic maps, no re-thresholded variants. - Never conclude "it's just noise" or "the decode failed" because the letters look faint or blobby. Faint glowing letters = success. Look for the word.
- Do not measure centroids/variance/correlation or invent alternative pipelines. None of that is needed; it only wastes turns and invites hallucination.
- Never OCR a raw frame — every frame is noise on its own.
- If one character is genuinely ambiguous, read the rest and mark just that one
(unclear: X). Keep the reply to the two images plus the single text line.
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.
- 5d ago First seen · 131 lines · 64 tokens per session scan A 44820d9373d5
ghost-decode is a skill published in the GitHub repository haroontrailblazer/ghost-font-decoder (10 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,814 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-08-31.
Other skills, from other repositories
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode…
adr-workflow
Scaffold, accept, index, and link Architectural Decision Records (ADRs). Use when the user says "write an ADR", "record this decision", "resolve [deferred item] with an ADR", "supersede ADR-NNNN", or otherwise wants to capture a hard-to-reverse decision in docs/decisions/. Also use when a refinement-todo entry needs…
explain
Explain jig vocabulary and artifacts in plain language. Three modes: term mode defines one lexicon term; artifact mode walks through a spec or ADR and its linked references; passage mode explains pasted jig output. Output is ephemeral (chat-only). Auto-triggers when you say explain this term, walk me through this…
clarify
Lightweight spec clarification scan for jig projects — a six-category ambiguity audit that asks up to five prioritized questions and appends them to the spec's ## Clarifications section. Auto-triggers when you say clarify this spec, audit this spec for ambiguities, is this spec ready for review, find unknowns in this…
reframe
Re-baseline a jig corpus onto a moved load-bearing reference by drafting a keystone ADR and an affected-artifact disposition manifest. Use when a vendor/API contract moved and specs and decisions must be re-anchored. Auto-triggers when you say reframe onto this, we changed direction, the design moved, or re-baseline…