present

A command that turns approved research findings into a self-contained, scrollable HTML presentation. It first checks a compiled research file and uses only claims marked as resolved.

In plain words
What is it for?
Use it to create slides covering the research problem, findings, tests, tradeoffs, recommendation, next steps, and evidence summary.
Why use it?
It prevents unresolved research disagreements from being presented as settled conclusions and gives the findings a defined slide structure.

Command

Install

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.

agentmods
npx agentmods add commands/grainulation/wheat/present
Clone the repo
git clone --depth 1 https://github.com/grainulation/wheat
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00462
Opus 5 $0.00000 $0.00231
Sonnet 5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

Measured yesterday against content hash 806739d3d269, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

present 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 yesterday.

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.

templates/commands/present.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/present — Generate a presentation from compiled claims

You are generating a presentation for this Wheat sprint. Same Bran compilation gate as /brief.

Process

  1. Run the compiler with check:

    npx @grainulation/wheat compile --check
    

    If blocked, STOP. Show errors, suggest fixes. Do not generate a presentation with unresolved conflicts.

  2. Read compilation.json — use ONLY resolved_claims.

  3. Generate presentation HTML: Create output/presentation.html — a self-contained, scroll-snap presentation using a dark theme.

    Structure the slides as:

    1. Title slide: Sprint question, date, audience
    2. The Problem: Why this research was needed (from constraint claims)
    3. What We Found: Key research findings (2-3 slides, from factual claims)
    4. What We Tested: Prototype and evaluation results (from tested claims)
    5. Tradeoffs: Risks and estimates
    6. Recommendation: The compiled recommendation with evidence
    7. Next Steps: Concrete actions
    8. Appendix: Compilation certificate, claim count, evidence summary

    Each slide should:

    • Be visually clean (use the dark theme, accent colors, cards)
    • Reference claim IDs subtly (small text at bottom of relevant sections)
    • Include data visualizations where relevant (CSS-only charts, comparison tables)
    • Work at any screen size (responsive)

Key rules

  • Same compilation gate as /brief — no presentation without passing compilation
  • Cite claims, but more subtly than the brief (this is for presenting, not auditing)
  • The presentation should tell a story: problem -> investigation -> evidence -> recommendation

Git commit

Stage output/presentation.html.

Commit: wheat: /present — generated presentation, certificate [hash]

Tell the user

  • Presentation is at output/presentation.html — open in browser, works for screen share
  • Mention the compilation certificate for reproducibility
  • Suggest /feedback after they present to capture stakeholder responses

Read the full file on GitHub · 56 lines

Changes

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.

  1. yesterday First seen · 56 lines · 0 tokens per session scan A 806739d3d269

Subscribe to this mod's changes

present is a command published in the GitHub repository grainulation/wheat (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 tokens. 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-30.