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 skills/stepzerolab/research-git/rgit-digestnpx skills add StepzeroLab/research-git --skill rgit-digestgit clone --depth 1 https://github.com/StepzeroLab/research-gitWhat 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.00076 | $0.00969 |
| Opus 5 | $0.00038 | $0.00485 |
| Sonnet 5 | $0.00015 | $0.00194 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
rgit-digest 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rgit-digest
Drains the history-digestion queue: deterministic staging through the rgit CLI, semantic segmentation via the capsule-segmenter subagent, non-interactive ingestion as origin=backfill capsules. Unlike live capture there is NO human approval gate — backfilled capsules are marked, filterable in recall, and bulk-removable (rgit digest clear).
Prerequisites: the repo is rgit init-ed and rgit digest scan has run (init usually does this; run it yourself if rgit digest status shows no units).
Locating the agent definitions. Same as rgit-capture: on Claude Code the plugin runtime resolves agent paths; on other CLIs resolve the plugin root from the skill symlink:
SKILL_REAL=$(realpath ~/.agents/skills/rgit-digest 2>/dev/null || readlink -f ~/.agents/skills/rgit-digest)
PLUGIN_ROOT=$(dirname "$(dirname "$SKILL_REAL")")
Process
1. Report the plan and agree on scope
Run rgit digest status --json. Tell the user: pending units, how many are dead experiments, estimated batches. Agree how many batches to run this session (default: keep going until the queue is empty or the user stops you).
2. Stage a batch
rgit digest next --batch 10 --json
Each item is {unit_id, kind, score, proposal_id, meta, diff, candidates, oversized}. meta carries commit subjects, dates, author — and for dead units the revert info (reverted_by / revert_subject / revert_date) when the death was a revert. Empty-diff units never appear (the engine skips them itself).
3. Dispatch capsule-segmenter per item (concurrently)
For each item, dispatch a subagent from agents/capsule-segmenter.md, passing proposal_id, repo_root, diff, and a history_context block built from meta: the commit subjects + dates + author, the revert info when present, oversized when true, and the note "historical diff — today's code may have refactored past it; write the resurrection guide against intent and structure". The subagent returns {"capsules": [...], "dropped": [...]}.
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 · 64 lines · 76 tokens per session scan A 0c61223b66e6
rgit-digest is a skill published in the GitHub repository StepzeroLab/research-git (42 stars, last pushed 26d ago), licensed MIT. It adds 76 tokens to every session and 969 once invoked, about $0.0004 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 skills, from other repositories
ts-sdk-author
Design, build, verify, and publish production-grade TypeScript SDKs as npm packages inside a pnpm monorepo. Covers workspace layout, public API and module boundaries, plugin extension points, branded types and library-tuned tsconfig, tsdown bundling (vs tsup/tsc-only/unbuild), package.json exports with dual ESM+CJS…
first-principles-thinking
Systematic first principles thinking for any problem domain. Use when the user says "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "is this the right approach", "challenge assumptions", "挑战假设", "为什么要这样做", "有没有更好的方案", "why are we doing it this way", or needs…
python-design
Python design patterns for CLI scripts and utilities — type-first development, deep modules, complexity management, and red flags. Use when reading, writing, reviewing, or refactoring Python files, especially in .trellis/scripts/ or any CLI/scripting context. Also activate when planning module structure, deciding…
contribute
Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation…
trellis-meta
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed…
trellis-meta
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed…