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.
git clone --depth 1 https://github.com/akshayrao14/git-practicesWrote 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/commands/akshayrao14/git-practices/session-compact-check)<a href="https://agentmods.dev/commands/akshayrao14/git-practices/session-compact-check"><img src="https://agentmods.dev/badge/commands/akshayrao14/git-practices/session-compact-check/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/commands/akshayrao14/git-practices/session-compact-check"><img src="https://agentmods.dev/badge/commands/akshayrao14/git-practices/session-compact-check.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.00037 | $0.00122 |
| Opus 5.5 | $0.00015 | $0.00049 |
| Sonnet 5.5 | $0.00007 | $0.00024 |
| Haiku 4.5 | $0.00004 | $0.00012 |
Grade A, and why
session-compact-check 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 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.
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.
What it actually says
Invoke the session-loop skill with focus=compact-check. Load sub/compact-check.md from the skill directory and follow it exactly.
Migrated from the standalone /compact-check command. If you have ~/.claude/commands/compact-check.md from before installing session-loop, both will coexist — remove the standalone one when you've confirmed /session-compact-check works.
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 · 8 lines · 37 tokens per session scan A 5faf89c78903
session-compact-check is a command published in the GitHub repository akshayrao14/git-practices (0 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 122 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
obsidian-checkin
Ask the owner whether old people and project notes still hold - shows what each note says and when it was last checked, re-asks until answered, saves the news.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
recall
Recall what MemOS knows about a topic as a token-budgeted context pack.
mem-search
Search past observations and context from claude-mem persistent memory.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.