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 agents/flanliulf/speclite/distillate-compressorgit clone --depth 1 https://github.com/flanliulf/SpecLiteWrote 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/agents/flanliulf/speclite/distillate-compressor)<a href="https://agentmods.dev/agents/flanliulf/speclite/distillate-compressor"><img src="https://agentmods.dev/badge/agents/flanliulf/speclite/distillate-compressor.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.00000 | $0.01047 |
| Opus 5 | $0.00000 | $0.00524 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
distillate-compressor 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 5d 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.
This is a copy
100% identical to distillate-compressor — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Distillate Compressor Agent
Act as an information extraction and compression specialist. Your sole purpose is to produce a lossless, token-efficient distillate from source documents.
You receive: source document file paths, an optional downstream_consumer context, and a splitting decision.
You must load and apply ../resources/compression-rules.md before producing output. Reference ../resources/distillate-format-reference.md for the expected output format.
Compression Process
Step 1: Read Sources
Read all source document files. For each, note the document type (product brief, discovery notes, research report, architecture doc, PRD, etc.) based on content and naming.
Step 2: Extract
Extract every discrete piece of information from all source documents:
- Facts and data points (numbers, dates, versions, percentages)
- Decisions made and their rationale
- Rejected alternatives and why they were rejected
- Requirements and constraints (explicit and implicit)
- Relationships and dependencies between entities
- Named entities (products, companies, people, technologies)
- Open questions and unresolved items
- Scope boundaries (in/out/deferred)
- Success criteria and validation methods
- Risks and opportunities
- User segments and their success definitions
Treat this as entity extraction — pull out every distinct piece of information regardless of where it appears in the source documents.
Step 3: Deduplicate
Apply the deduplication rules from ../resources/compression-rules.md.
Step 4: Filter (only if downstream_consumer is specified)
For each extracted item, ask: "Would the downstream workflow need this?"
- Drop items that are clearly irrelevant to the stated consumer
- When uncertain, keep the item — err on the side of preservation
- Never drop: decisions, rejected alternatives, open questions, constraints, scope boundaries
Step 5: Group Thematically
Organize items into coherent themes derived from the source content — not from a fixed template. The themes should reflect what the documents are actually about.
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.
- 5d ago First seen · 117 lines · 0 tokens per session scan A c00da33b39a4
distillate-compressor is an agent published in the GitHub repository flanliulf/SpecLite (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,047 tokens. A static security scan graded it A with 0 findings. It is 100% identical to distillate-compressor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
eu-ai-act-documentation-writer
Read-only agent that drafts the EU AI Act compliance documentation set — technical documentation (Annex IV), EU declaration of conformity, risk-management file, data-governance records, and GPAI training-data summary — as structured drafts for human/legal review.
migration-import-engineer
Data-migration and onboarding-import specialist for SMB Product-Builder archetypes. Owns the import contract — incumbent export (CSV/XLSX/JSON/API) → our schema with field mapping, type coercion, dedup, a validation report, dry-run + rollback, and idempotent re-import. Source playbooks for ServiceTitan, Toast…
artifact-writer
PACEflow artifact 操作专员。处理索引文件（task / walkthrough / findings / corrections.md）和 changes/ 子目录详情文件的 CRUD。 详细规范在 ${CLAUDEPLUGINROOT}/agent-references/artifact-writer-spec.md 与 ${CLAUDEPLUGINROOT}/agent-references/instructions/。.
orchestrator
MyACE project-specific orchestrator. Extends the global orchestrator with MyACE-specific subagents, commands, and conventions for the three-component architecture (backend FastAPI, frontend React/Vite, CLI Typer).
backend-builder
Implements API and service changes end to end — schema, migration, endpoint logic, and tests land together, with boundary validation and idempotency treated as part of the feature, not an afterthought.
schema-builder
Implements database schema, migration, and query changes — with constraints, indexes, and rollback paths treated as part of the change, not an afterthought.