Borrowing it
Nothing to install: this file belongs to jiadizhunine/deepPPT. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiadizhunine/deepPPT/main/AGENTS.mdgit clone --depth 1 https://github.com/jiadizhunine/deepPPTWrote 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/jiadizhunine/deepppt/agents-md)<a href="https://agentmods.dev/instructions/jiadizhunine/deepppt/agents-md"><img src="https://agentmods.dev/badge/instructions/jiadizhunine/deepppt/agents-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.1 | $0.01300 | $0.01300 |
| Opus 5 | $0.00650 | $0.00650 |
| Sonnet 5 | $0.00260 | $0.00260 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
deepPPT 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 6d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deepPPT collaboration rules
Source and licensing
- Add only project-owned implementations or material with a verified, compatible redistribution license.
- Do not copy or adapt code or documentation from
anthropics/skills/skills/pptx, PPTAgent, Codex Slides, or another source unless its license permits this repository's use and every required notice is included. Architectural ideas must be independently implemented. - Before bundling third-party code, schemas, templates, or assets, verify the license and add every required attribution, notice, and license text.
- Existing PPTX files are content sources only. Extract approved content and rebuild a separate deck; do not add a generic package-editing toolkit.
Visual contract
The bottom red key-finding box is opt-in, not a content-slide default. Use it only for a decisive, non-duplicative takeaway, record the reason in the deck plan, keep the total at or below one third of all slides, and keep the example decks free of runs of three or more consecutive red boxes.
Deck-wide sequence checks must follow the slide order declared in
ppt/presentation.xml; never infer presentation order from slideN.xml file
names. Resolve relationship targets with the shared OPC resolver; root-absolute
targets such as /ppt/slides/slide1.xml are valid package paths and must not be
assembled with string concatenation. Validate only relationships referenced by
the declared slide order; unused relationship records must not block extraction
or layout QA.
Every [Content_Types].xml override must resolve to an existing package part.
Notes masters must not share a theme part with slide masters; PowerPoint repairs
that PptxGenJS package shape on open. Keep both cases in normalize_pptx.py,
check_pptx.py, and regression coverage.
Use one user-approved release PR and resolve actionable feedback on that same branch. Do not create review-only PRs, follow-up PRs whose sole purpose is to trigger another review, or recursive repair/review loops. Before merge or release, run one review gate on the final intended head and verify that no actionable thread remains unresolved; repeat only after a substantive code change or an explicit user request.
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.
- 6d ago First seen · 112 lines · 1,300 tokens per session scan A eb20dae96ffb
deepPPT AGENTS.md is an instructions file published in the GitHub repository jiadizhunine/deepPPT (25 stars, last pushed 28d ago), licensed MIT. It adds 1,300 tokens to every session, about $0.0065 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-30.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.