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 akaieuan/Hologram --skill statusgit clone --depth 1 https://github.com/akaieuan/HologramWrote 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/akaieuan/hologram/status)<a href="https://agentmods.dev/skills/akaieuan/hologram/status"><img src="https://agentmods.dev/badge/skills/akaieuan/hologram/status/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/akaieuan/hologram/status"><img src="https://agentmods.dev/badge/skills/akaieuan/hologram/status.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.00087 | $0.00424 |
| Opus 5 | $0.00044 | $0.00212 |
| Sonnet 5 | $0.00017 | $0.00085 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
Hologram pipeline status 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.
What it actually says
Hologram pipeline status
A catch-up read. pipeline_status scans the recent event log and buckets it
into the three things you usually want to know — no Blender, no re-running
checks, just what already happened.
What to do
-
Call
pipeline_status. You get back:failures— recent failed tool calls, each with its error textlast_check— the most recenthologram checksummary (assets / checks / errors / warnings)recent_diffs— assets whose fingerprint changed since their last checkpoint (lost / gained / changed counts)
-
Lead with the headline. "Two failures in the last hour, last check was clean, one asset gained a material." Then the detail. If everything's quiet, say so — a calm pipeline is a valid answer.
-
Need the raw timeline?
tail_events(limit)returns recent events newest-first if they want the play-by-play instead of the summary.
Notes
- This reflects the last emitted check — it does not run checks itself (the
MCP server never loads user code). If the summary looks stale, run
/hologram:checkto refresh it. - Diffs are recorded against the baseline from the last
hologram check, so "changed" means "since you last checked".
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 · 37 lines · 87 tokens per session scan A af32a2640912
Hologram pipeline status is a skill published in the GitHub repository akaieuan/Hologram (2 stars, last pushed 1mo ago), licensed MIT. It adds 87 tokens to every session and 424 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-08-31.
Other skills, from other repositories
kiln
3D asset production pipeline via Blender MCP — sourcing, AI generation, cleanup, texturing, optimization, export. Batch mode for autonomous multi-asset production.
using-blender
General Blender workflow skill for AI agents working with .blend, .fbx, .obj, .glb, glTF, materials, scene inspection, bpy automation, headless Blender batch runs, export/reimport validation, previews, and optional Blender MCP control. Use when a task asks to open, inspect, create, automate, convert, optimize, render…
ikea-model-collector
Collect user-observed IKEA product GLB models into verified local research collections with provenance, dimensions, optional Blender previews, a Three.js gallery, indexes, and handoff. Use when Codex is asked to find an IKEA product's available 3D model, process a user-specified product list, import browser-captured…
dashboard-design
Use this skill first when the user wants to design or plan a dashboard, especially Vizro dashboards. Enforces a 3-step workflow (requirements, layout, visualization) before implementation. Activate when the user asks to create, design, or plan a dashboard. For implementation, use the dashboard-build skill after…
selecting-vizro-charts
Use this skill when choosing chart types, applying Plotly Express conventions, configuring colors, building KPI cards, or adding tables (AG Grid) to Vizro dashboards. Activate when the user asks which chart fits their data, needs custom chart functions, wants to set colors or palettes, is creating KPI metric cards, or…
social-media-matrix
A multi-platform social media tracking dashboard that compares platforms and metrics in a table-like view. It includes charts, an insights panel, and a grid of top posts.