slideforge-mcp: Instructions file for Codex

AGENTS.md

slideforge-mcp AGENTS.md is an instructions file for Codex, OpenCode from smartdatabrokers/slideforge-mcp. It costs 1,382 tokens per session, scanned A, original, MIT.

Instructions for using SlideForge, a service that turns structured slide requests into editable PowerPoint files. It uses predefined slide layouts and reports which content was used exactly versus completed by the model.

In plain words
What is it for?
Use them when an agent must create .pptx presentations through SlideForge, including charts, timelines, funnels, tables, and organizational diagrams.
Why use it?
They explain how to connect to the service and choose an appropriate slide layout before creating a presentation. This helps an agent produce editable slides with clear content provenance.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: positional $N argument; mentions Claude Code; mentions Codex.

This is smartdatabrokers/slideforge-mcp's own configuration. It tells Codex and OpenCode how to work on slideforge-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything slideforge-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to smartdatabrokers/slideforge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/smartdatabrokers/slideforge-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/smartdatabrokers/slideforge-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for slideforge-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/smartdatabrokers/slideforge-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/smartdatabrokers/slideforge-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/smartdatabrokers/slideforge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/smartdatabrokers/slideforge-mcp/agents-md/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.

agentmods 80×15 button for slideforge-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/smartdatabrokers/slideforge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/smartdatabrokers/slideforge-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,382 This file is loaded in full into every session.
When invoked 1,382 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01382 $0.01382
Opus 5.5 $0.00553 $0.00553
Sonnet 5.5 $0.00276 $0.00276
Haiku 4.5 $0.00138 $0.00138

Measured 2mo ago against content hash 2b9d07171d73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

slideforge-mcp AGENTS.md 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 2mo 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.

AGENTS.md · 82 lines

How it starts

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

SlideForge — agent instructions

SlideForge (slideforge.dev, by Smart Data Brokers GmbH) turns typed slide intents into native, fully editable PowerPoint files. It is a compiler, not a generator: a deterministic engine renders 200+ catalog patterns from structured content — no LLM in the render path — and every response carries a fidelity manifest stating what was bound verbatim vs. model-completed. Copy this file (or its rules) into a project where an agent produces .pptx deliverables.

Connect

MCP (preferred — tools + schemas are self-describing):

# Claude Code
claude mcp add --transport http slideforge https://api.slideforge.dev/mcp/
# Codex CLI / Cursor / Windsurf: streamable-http MCP server at the same URL,
# header "Authorization: Bearer sf_live_YOUR_KEY"

REST (everything also works without MCP): https://api.slideforge.dev/v1/… with the same Bearer key. Reference: https://slideforge.dev/docs/api — machine-readable rate card at GET /v1/pricing.

The workflow that works

  1. Discover the form. browse_catalog (or GET /v1/catalog) → pick a form (kpi_metrics, waterfall_bridge, gantt_plan, org_structure, funnel, data_table, …). browse_catalog type=schema form=<form> returns the JSON Schema and a copy-pasteable example intent — start from the example, swap in real content, keep the field names. Unsure which form? plan_slide with the brief is free.
  2. Dry-run first. Send the intent with dry_run: true → validation + a fidelity forecast at $0. Fix errors[] (each has a machine code + remedy), then resend without dry_run.
  3. Render. create_slide (one) or create_deck (slides[], parallel, failed slides are isolated and free). $0.05/slide, usable-or-free: a render with blocking errors never bills.
  4. Verify like an agent. The preview PNG is embedded inline in the tool result — look at it before declaring done, no fetch needed. Download the deliverable via header-auth: GET /v1/jobs/<job_id>/pptx with Authorization: Bearer sf_live_YOUR_KEY. To hand off a shareable link, POST /v1/jobs/<job_id>/download-url mints a short-TTL single-use one.
  5. Trust the manifest, not vibes. fidelity: verbatim = every number/word came from your input. ai_completed/mixed = the response names which fields a model filled. partial = some supplied content didn't make it onto the slide — the manifest names what was dropped; never deliver a partial render without telling the user what's missing. Surface fidelity to the user when the content is business data.

Read the full file on GitHub · 82 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. 2mo ago First seen · 82 lines · 1,382 tokens per session scan A 2b9d07171d73

Subscribe to this mod's changes

slideforge-mcp AGENTS.md is an instructions file published in the GitHub repository smartdatabrokers/slideforge-mcp (4 stars, last pushed 2mo ago), licensed MIT. It adds 1,382 tokens to every session, about $0.0055 per session on Opus 5.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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens