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 instructions/teknologika/deckbuilder/claude-mdgit clone --depth 1 https://github.com/teknologika/DeckbuilderWrote 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/instructions/teknologika/deckbuilder/claude-md)<a href="https://agentmods.dev/instructions/teknologika/deckbuilder/claude-md"><img src="https://agentmods.dev/badge/instructions/teknologika/deckbuilder/claude-md.svg" alt="Measured on agentmods" 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 | $0.04922 | $0.04922 |
| Opus 5 | $0.02461 | $0.02461 |
| Sonnet 5 | $0.00984 | $0.00984 |
| Haiku 4.5 | $0.00492 | $0.00492 |
Grade A, and why
Deckbuilder CLAUDE.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 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 — 522 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md or GEMINI.md
Project Overview
THE THREE LAWS OF AI CODING
LAW 1 - An AI may not reduce the quality of a codebase or, through inaction, allow a codebase's quality to be reduced.
LAW 2 - An AI must obey orders from humans, unless such orders are unclear, or conflict with the First Law.
LAW 3 - An AI must follow the prime directives, provided this does not conflict with the First or Second Law.
IMPORTANT AI PRIME DIRECTIVES
1. ALWAYS, ALWAYS WORK ON A BRANCH
2. ALWAYS ENSURE CODE IS HIGH QUALITY, AND MEETS DRY PRINCIPLES
3. MAKE CHANGES THAT ENHANCE AND IMPROVE THE CODEBASE
4. ALWAYS TRY AND ENHANCE EXISTING CODE, AND MINIMISE CYCLOMATIC COMPLEXITY, DONT CREATE ALTERNATE CODE PATHS
5. DOCUMENT CODE IN A WAY THAT MAKES IT EASY FOR AI TO NAVIGATE THE CODE BASE
6. TESTS, PRE-CHECKIN HOOKS AND CI ARE GUARDRAILS. NEVER FAKE RESULTS OR WORK AROUND THEM WITH --NO-VERIFY
7. ALWAYS USE AUSTRALIAN ENGLISH, AND THE METRIC SYSTEM
About this project
Deckbuilder is a Python library and accompanying MCP (Model Context Protocol) Server for intelligent PowerPoint presentation generation. The project has evolved beyond initial setup into a comprehensive content-first presentation intelligence system.
Testing the application
The easiset way is to use the CLI drectly then use python-pptx to verify your output e.g.
Bash(source .venv/bin/activate && deckbuilder create tests/output/imput_file.md --output tests/output/ouput_file)
🔄 Project Awareness & Context
- Always read
PLANNING.mdat the start of a new conversation to understand the project's architecture, goals, style, and constraints. - Check
TASK.mdbefore starting a new task. If the task isn’t listed, add it with a brief description and today's date. - Use consistent naming conventions, file structure, and architecture patterns as described in
PLANNING.md.
🧱 Code Structure & Modularity
- Never create a file longer than 500 lines of code. If a file approaches this limit, refactor by splitting it into modules or helper files.
- Organize code into clearly separated modules, grouped by feature or responsibility.
- Use clear, consistent imports (prefer relative imports within packages).
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 · 522 lines · 4,922 tokens per session scan A 91a29ed0106e
Deckbuilder CLAUDE.md is an instructions file published in the GitHub repository teknologika/Deckbuilder (7 stars, last pushed 1y ago), licensed Apache-2.0. It adds 4,922 tokens to every session, about $0.0246 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 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.