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 skills add 5queezer/distill --skill seedgit clone --depth 1 https://github.com/5queezer/distillWrote 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/skills/5queezer/distill/seed)<a href="https://agentmods.dev/skills/5queezer/distill/seed"><img src="https://agentmods.dev/badge/skills/5queezer/distill/seed/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/5queezer/distill/seed"><img src="https://agentmods.dev/badge/skills/5queezer/distill/seed.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01028 |
| Opus 5.5 | $0.00000 | $0.00411 |
| Sonnet 5.5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
seed scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://127.0.0.1:${DISTILL_INGEST_PORT:-21746}/observe \ How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed Knowledge Base from Git History
Populate the distill MCP knowledge base from the current repo's git history. Extracts decisions, patterns, failures, and context from commits and stores them with correct metadata.
Prerequisites
distillMCP server running withsearch_memoryandupdate_memorytools available- Ingest HTTP endpoint running (started automatically with the MCP server)
- Inside a git repository
Workflow
1. Survey the repo
REPO_NAME=$(basename $(git rev-parse --toplevel))
COMMIT_COUNT=$(git rev-list --count HEAD)
echo "$REPO_NAME: $COMMIT_COUNT commits"
git log --oneline --reverse | head -20
git log --oneline --reverse | tail -20
Report the repo name and commit count to the user. Ask if they want to seed all commits or a date range.
2. Process commits in batches of 10
git log --reverse --format="%H %aI %s" [--since="YYYY-MM-DD"]
For each commit:
Extract the timestamp — use the commit's author date (%aI), NEVER the current time.
Classify the commit:
| Type | What to extract | Example |
|---|---|---|
decision |
Chose X over Y because Z | "Replaced SQLite with asyncpg for stateless GKE deployment" |
pattern |
Recurring convention | "All services use structlog with JSON output to stderr" |
failure |
Tried X, abandoned because Y | "Tried Redis for persistence, reverted — too complex for single-node" |
dependency |
Service A depends on B | "Parser requires pgvector extension >= 0.5" |
context |
Migration/state at a point in time | "Auth middleware rewrite started, driven by compliance requirements" |
Skip these:
chore:formatting, linting, dep bumps without rationale- Merge commits with no original content
fix:typos, whitespace, trivial CI tweaks
Short commit messages (1-2 lines): Read the diff — the real decision is in the code.
git show <hash> --stat
git show <hash> -- <relevant files>
Long/AI-generated messages: The message IS the knowledge. Skim code only if unclear.
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.
- 1mo ago First seen · 123 lines · 0 tokens per session scan A bac17946ba71
seed is a skill published in the GitHub repository 5queezer/distill (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,028 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.
recall-rationale
Recall why a past change was made by locating the Claude Code transcript that produced it. Use when the user asks to "recall the rationale", "find the rationale", "look up the rationale", "why did I do X", "why did we do X", "why was this changed", or "find the transcript for this commit".
release-finalizer
Merges a release PR, associates it with resolved issues, replies to issue reporters, and closes issues. Use after PR review is complete and ready for merge. Closes the release cycle.