deckforge AGENTS.md

Repository instructions for DeckForge, a project for building editable presentations that run in a web browser. They define which rules and skills agents must read for different types of work.

In plain words
What is it for?
Creating, redesigning, extending, migrating, reviewing, planning, publishing, or visually verifying browser-based slide applications.
Why use it?
They help agents use the right guidance for implementation, review, planning, publishing, and visual checking instead of treating every presentation task the same way.

Instructions file for CodexOpenCode

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 instructions/tph-kds/deckforge/agents-md
Clone the repo
git clone --depth 1 https://github.com/tph-kds/deckforge

Made for: Codex, OpenCode.

Per session 498 This file is loaded in full into every session.
When invoked 498 The same file — it is already loaded in full.
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.00498 $0.00498
Opus 5 $0.00249 $0.00249
Sonnet 5 $0.00100 $0.00100
Haiku 4.5 $0.00050 $0.00050

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

Security

Grade A, and why

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

AGENTS.md · 60 lines

How it starts

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

DeckForge Agent Entry Point

This repository contains Agent Skills and reference scaffolds for reliable editable, browser-native slide applications.

Code intelligence

Prefer Serena semantic tools for source-code navigation, symbol lookup, references, implementations, dependency tracing, and symbol-level refactoring.

Use built-in read/grep tools for configuration files, documentation, logs, plain-text searches, or when Serena cannot resolve the required code context.

Read order

  1. rules/README.md
  2. rules/repository-boundaries.md
  3. rules/design-quality.md
  4. rules/security-rules.md
  5. the relevant skills/*/SKILL.md
  6. skills/deckforge/references/delivery-acceptance-contract.md for implementation work

Default routing

  • Use skills/deckforge/SKILL.md for creating, redesigning, extending, or migrating a presentation product.
  • Use skills/deckforge-audit/SKILL.md for review-only work.
  • Use skills/deckforge-runtime-planner/SKILL.md for architecture planning without implementation.
  • Use skills/deckforge-publish/SKILL.md for publishing, embedding, and delivery.
  • Use skills/deckforge-visual-evidence/SKILL.md for browser-based verification of a generated application and for producing executed capability evidence.
  • Use skills/deckforge-skill-evaluator/SKILL.md for comparing skill conditions and gatekeeping skill releases.

For ordinary end-user requests to create slides, select the editable-deck profile unless the user explicitly asks for a presenter-only artifact.

Non-negotiable implementation rules

  • Use semantic layout slots rather than arbitrary coordinates by default.
  • Do not claim an editor exists unless controls mutate DeckProject state and changes persist.
  • Keep the editor and presenter as separate surfaces.
  • Provide visible shortcut guidance.
  • Run schema, layout, output-contract, build, and behavioral checks before completion.

Plugin discovery

  • .agents/plugins/marketplace.json
  • .claude-plugin/plugin.json
  • .codex-plugin/plugin.json

Read the full file on GitHub · 60 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 · 60 lines · 498 tokens per session scan A 41da07c17bb5

Subscribe to this mod's changes

deckforge AGENTS.md is an instructions file published in the GitHub repository tph-kds/deckforge (4 stars, last pushed 15d ago), licensed MIT. It adds 498 tokens to every session, about $0.0025 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.