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 metagit-ai/metagit-cli --skill metagit-context-packgit clone --depth 1 https://github.com/metagit-ai/metagit-cliWrote 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/metagit-ai/metagit-cli/metagit-context-pack)<a href="https://agentmods.dev/skills/metagit-ai/metagit-cli/metagit-context-pack"><img src="https://agentmods.dev/badge/skills/metagit-ai/metagit-cli/metagit-context-pack/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/metagit-ai/metagit-cli/metagit-context-pack"><img src="https://agentmods.dev/badge/skills/metagit-ai/metagit-cli/metagit-context-pack.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.00048 | $0.02834 |
| Opus 5 | $0.00024 | $0.01417 |
| Sonnet 5 | $0.00010 | $0.00567 |
| Haiku 4.5 | $0.00005 | $0.00283 |
Grade A, and why
metagit-context-pack 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 9d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metagit context packs
Use this skill for the most token-efficient way to onboard into a metagit workspace.
Prefer metagit context pack --tier N --json over reading raw trees or full manifests.
Set non-interactive defaults:
export METAGIT_AGENT_MODE=true
Run from the umbrella repo that contains .metagit.yml (or pass -c path/to/.metagit.yml).
When to use
- Session start in any metagit-managed workspace
- Before editing — need project/repo boundaries and health without cloning everything
- Returning after idle — tier 2 digest shows what changed since last session
- Scoping a bugfix — tier 1 cards +
repomixprofile instead of whole-repo dumps - Coordinating humans and agents — objectives and approval queue state
Do not skip context packs and grep the filesystem when a manifest exists.
Tier workflow
| Tier | Command | Typical tokens | Contents |
|---|---|---|---|
| 0 | metagit context pack --tier 0 --json |
~100–400 | Workspace map: projects, repos, paths, clone status |
| 1 | metagit context pack --tier 1 --json |
+200–600/repo | Tier 0 + repo cards (git state, stack hints, health flags) |
| 2 | metagit context pack --tier 2 --json |
+digest | Tier 1 + session digest; updates session boundary |
Escalate tiers only when needed. Narrow tier 1/2 with --project and/or --repo.
Primary session command
metagit context pack --tier 2 --json -c .metagit.yml
Pair with operational prompts (paste --text-only output into agent context):
metagit prompt workspace -k session-start --text-only -c .metagit.yml
metagit prompt workspace -k context-pack --text-only -c .metagit.yml # tier escalation guide
Escalation rules
- Start tier 0 when you only need catalog boundaries (search-before-create, layout planning).
- Move to tier 1 when git health, stack hints, or per-repo instructions matter.
- Use tier 2 at session open/return — digest includes
first_session,manifest_changed, per-repo commit counts, active objective id. - Tier 2 touches the session boundary — avoid running it from multiple agents simultaneously on a shared manifest (see multi-instance below).
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.
- 9d ago First seen · 278 lines · 48 tokens per session scan A fea6dbf939ae
metagit-context-pack is a skill published in the GitHub repository metagit-ai/metagit-cli (3 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 2,834 once invoked, about $0.0002 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.
Other skills, from other repositories
memory-commit
Use when the user explicitly says "remember this", "save this", "ghi nho", "luu lai", "save for next time", or otherwise asks to persist the immediately preceding context. Captures with the appropriate contexttype (decision, preference, fact, skill, task, conversation) so future sessions can retrieve it accurately.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
clawrium-release-announcements
Daily — draft a release blog post, open a PR, iterate on comments until merged.
blog-author
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
release-watcher
Watch upstream Claw releases and clawrium discussions; surface top 3 feature candidates to Devashish via Discord DM for approve/skip.
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.