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 mehdiforoozandeh/crux --skill prezitgit clone --depth 1 https://github.com/mehdiforoozandeh/cruxWrote 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/mehdiforoozandeh/crux/prezit)<a href="https://agentmods.dev/skills/mehdiforoozandeh/crux/prezit"><img src="https://agentmods.dev/badge/skills/mehdiforoozandeh/crux/prezit/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/mehdiforoozandeh/crux/prezit"><img src="https://agentmods.dev/badge/skills/mehdiforoozandeh/crux/prezit.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.00161 | $0.02156 |
| Opus 5 | $0.00081 | $0.01078 |
| Sonnet 5 | $0.00032 | $0.00431 |
| Haiku 4.5 | $0.00016 | $0.00216 |
Grade A, and why
prezit 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 11d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
prezit — presentations from a subtree
One anchor, one story. The body of the deck is the anchor and everything under it; the intro is built from the anchor's ancestors and the wiki pages they link. A hypothesis anchor is legal and yields a shorter deck. No time-window, no multi-anchor: "what happened this week" is answered by choosing the anchor whose subtree moved.
The three-way split (who does what)
| part | who | what |
|---|---|---|
crux deck <anchor> --json |
engine | the entire story material, assembled deterministically |
assets/deck.html |
this skill's template | all chrome: palette, fade, keyboard nav, progress, DOM-derived count |
| the deck's prose + charts | you, the agent | narrative selection, the hero figures, the bullets |
crux deck --verify/--refresh/--lint |
engine | proves numbers match; repairs values; checks the slide contract |
You never retype the chrome (copy the template), and you never let the engine author a sentence — selection and phrasing are your whole job.
The mapping — what each crux object becomes
| crux object | role in the deck |
|---|---|
| ancestors of the anchor (root → parent) | grand motivation — the line of reasoning |
| wiki pages linked from anchor + ancestors | background for the intro |
| sibling questions | the map of the larger problem |
| the anchor question | the question slide; its ## Protocol → the "rules locked up front" note |
| child hypotheses | the bridge from question to method |
RD pages (once the RD layer exists; rd is empty until then) |
methods |
| verifiables + ticks + findings | the results claims, and the honest negatives |
results/<hid>/ artifacts |
the figures |
| approved synthesis | the verdict / next-steps slide — dropped when none is approved |
| child states (idea/staged vs done) | scope — executed vs parked |
Shorthand: intro = wiki, methods = design (not implementation legwork), results = tree.
Workflow
- Harvest.
crux deck <anchor> --jsonfrom inside the vault. On a large vault you may delegate the initial sweep to a read-only search subagent — it returns paths and structure only. - Read end to end. Every linked report under
results/<hid>/, every finding, the approved synthesis. Inventory the figures and themetrics.jsonaddresses. - Agree the arc with the PI before drafting. Structured questions, each with a
recommended default: single arc vs mini-arc per sub-question; redesign figures from
metrics.jsonvs reuse; which 1–3 findings get a slide. Trivia (output path, framework) is stated, not asked. - Draft. Copy
assets/deck.htmlto<vault>/presentations/<anchor-id>/index.htmland fill the stubs. Studyexamples/q1_scaling_deck.html— it is the worked example, built onskills/crux/examples/scaling_vaultq1, verify-green and lint-clean. - Check.
crux deck --verify <deck> --strictandcrux deck --lint <deck>until both are green. Then the manual pass: open fromfile://, walk every slide at 16:9, confirm nothing collides with the fixed footer and in-SVG text is room-legible. - Refine with the PI. Deck-building is a refinement loop by nature — "split that slide", "drop that model everywhere", "enlarge the figures" each must be a small local edit. That is why this is a skill, not a fire-and-forget agent.
- Re-presenting later:
crux deck --refresh <deck>, then re-read the prose around every changed number — refresh fixes values; only a human fixes the sentence that interprets them ("clears the floor by +0.05" can be silently falsified by a correct refresh).validate --check=decksreports stale decks from the vault side.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 155 lines · 161 tokens per session scan A 5e32247d3940
prezit is a skill published in the GitHub repository mehdiforoozandeh/crux (6 stars, last pushed 6d ago), licensed MIT. It adds 161 tokens to every session and 2,156 once invoked, about $0.0008 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
chengfeng-check-updates
An environment manager for a video-editing system. It checks whether its skills and runtime—the software needed to run them—are installed and compatible.
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.