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/steipete/summarize/agents-mdgit clone --depth 1 https://github.com/steipete/summarizeWhat 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.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
summarize 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 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.
How it starts
The opening of the file, as written. The whole thing — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Guardrails
- Hard rule: single source of truth =
~/Projects/summarize; never commit invendor/summarize(treat it as a read-only checkout). - Note: multiple agents often work in this folder. If you see files/changes you do not recognize, ignore them and list them at the end.
Workspace layout (note)
- Monorepo (pnpm workspace).
- Packages:
@steipete/summarize= CLI + UX (TTY/progress/streaming). Depends on core.@steipete/summarize-core(packages/core) = library surface for programmatic use (Sweetistics etc). No CLI entrypoints.
- Versioning: lockstep versions; publish order: core first, then CLI (
scripts/release.sh/RELEASING.md). - Homebrew/core formula is not owned here; BrewTestBot autobumps releases about every 3h. Do not block or manually manage it; ship and continue.
- Chrome Web Store: every release must upload the matching
dist-chrome/summarize-chrome-extension-v<version>.zipto itemcejgnmmhbbpdmjnfppjdfkocebngehfg, submit it for review with automatic publishing, and verify the exact pending/published version. Skip only when every shipped change is daemon-side and the packaged extension/companion contract is unchanged. - Dev:
- Build:
pnpm -s build(builds core first) - Gate:
pnpm -s check - Import from apps: prefer
@steipete/summarize-coreto avoid pulling CLI-only deps.
- Build:
- Dependencies: stable releases need a 7-day stabilization delay before adoption; prereleases remain excluded unless already adopted.
- Daemon: restart with
pnpm -s summarize daemon restart; verify viapnpm -s summarize daemon status. - Rebuild (extension + daemon): run both in order:
pnpm -C apps/chrome-extension buildpnpm summarize daemon restart
- Extension tests:
pnpm -C apps/chrome-extension test:chrome= supported automated path.- Firefox Playwright extension tests are not reliable (
moz-extension://limitation); defaulttest:firefoxskips. - Use
pnpm -C apps/chrome-extension test:firefox:forceonly for explicit diagnostics.
- Commits: use
committer "type: message" <files...>(Conventional Commits).
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.
- 2d ago First seen · 29 lines · 543 tokens per session scan A e112a743af82
summarize AGENTS.md is an instructions file published in the GitHub repository steipete/summarize (6,588 stars, last pushed yesterday), licensed MIT. It adds 543 tokens to every session, about $0.0027 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
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.
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).
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.