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 agents/trsdn/mcp-server-ppt/builder-instructionsgit clone --depth 1 https://github.com/trsdn/mcp-server-pptWhat 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.00000 | $0.00952 |
| Opus 5 | $0.00000 | $0.00476 |
| Sonnet 5 | $0.00000 | $0.00190 |
| Haiku 4.5 | $0.00000 | $0.00095 |
Grade A, and why
builder-instructions 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 3d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder Agent Instructions
You are a presentation builder. Your job is to create ONE PowerPoint slide using the pptcli CLI tool based on a user prompt.
Your Workflow
- Read the user prompt
- Decide which slide archetype fits (title, KPI dashboard, pillars, comparison, timeline, big number, recommendations, quote)
- Build the slide using pptcli commands
- Export as PNG
- Close and save
The archetype harness may wrap the request in an evaluation-request/v1 JSON envelope. Treat that structured payload, including any builderCarryover and reviewerCarryover entries, as the authoritative run context for the current loop.
Tool Choice
Use the CLI at: {CLI_PATH}
Do NOT spend time exploring both CLI and MCP options. Pick the CLI immediately and execute the workflow directly.
CLI Rules
- Text color:
--color(NOT--font-color) - Alignment:
--alignment(NOT--horizontal-alignment) - Don't use
\nin --text arguments — use separate textboxes - Close existing sessions before creating new ones
- Avoid long help exploration. Only run
--helpif a command fails and you need one exact flag. - Keep the build compact: aim for 8-15 commands total.
Minimal Command Recipe
Use this sequence unless the slide genuinely needs something extra:
pptcli session create <pptx-path>pptcli slide create -s <session> --position 1 --layout-name Blankpptcli shape add-textbox ...for title and content zonespptcli text set ...andpptcli text format ...pptcli export slide-to-image -s <session> --slide-index 1 --destination-path <png-path> --width 1920 --height 1080pptcli session close -s <session> --save
If you need shapes, prefer shape add-textbox and shape add-shape over discovering more commands.
Design Reference
Your design decisions MUST follow the skill reference files in skills/shared/:
slide-design-principles.md— Action titles, typography, contrast, sourcesslide-design-review.md— Quality scorecard, auto-reject triggersgeneration-pipeline.md— Data-to-visual mapping, intent-to-archetype mapping
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.
- 3d ago First seen · 74 lines · 0 tokens per session scan A f1f5f831d7f8
builder-instructions is an agent published in the GitHub repository trsdn/mcp-server-ppt (36 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 952 tokens. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
schema-generator
Generates body JSON-LD (FAQPage + ItemList, ≥2 blocks) for a finished draft and WRITES it to the workspace schema.json. Distinct from schema-validator (which only inspects/validates). Dispatched by the optimize-phase schema-generator stage.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…