pptwise CLAUDE.md

Project instructions for developing pptwise, a software project that creates or processes PowerPoint presentations. They define required checks, documentation reading, branch naming, and dependency rules.

In plain words
What is it for?
Use them when modifying pptwise, especially for documentation work, dependency changes, command-line behavior, or presentation rendering.
Why use it?
They give a coding agent the project’s working rules before it changes code. This helps avoid skipped checks, incorrect branches, and unsupported dependencies.

Instructions file

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/liustack/pptwise/claude-md
Clone the repo
git clone --depth 1 https://github.com/liustack/pptwise
Per session 194 This file is loaded in full into every session.
When invoked 194 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.00194 $0.00194
Opus 5 $0.00097 $0.00097
Sonnet 5 $0.00039 $0.00039
Haiku 4.5 $0.00019 $0.00019

Measured 2d ago against content hash 4b797628ca94, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pptwise 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 2d 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.

CLAUDE.md · 13 lines

What it actually says

CLAUDE.md

  1. Read AGENTS.md
  2. Run pnpm docs:list, then read the docs/*.md relevant to the task

Iron rules

  1. Open a topic branch (feat/ fix/ refactor/ docs/ chore/ prefix) before touching main
  2. pnpm check is the default acceptance gate. Also run pnpm e2e when the render chain changes
  3. The src/index.ts dependency closure must stay free of Node-only deps (commander/linkedom/sharp are only allowed under src/cli* and src/platform/node.ts)
  4. Never blindly pass -u on snapshot failures. Find the root cause first
  5. Public surfaces (CLI output/error messages/README/JSDoc) are in English. Chinese comments in migrated code stay as-is
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. 2d ago First seen · 13 lines · 194 tokens per session scan A 4b797628ca94

Subscribe to this mod's changes

pptwise CLAUDE.md is an instructions file published in the GitHub repository liustack/pptwise (10 stars, last pushed 2d ago), licensed MIT. It adds 194 tokens to every session, about $0.0010 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.

Related

Other instructions, from other repositories