Borrowing it
Nothing to install: this file belongs to TechHU-GS/cc-discipline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TechHU-GS/cc-discipline/main/.claude/skills/summary/SKILL.mdgit clone --depth 1 https://github.com/TechHU-GS/cc-disciplineWrote 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/techhu-gs/cc-discipline/summary)<a href="https://agentmods.dev/skills/techhu-gs/cc-discipline/summary"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/summary/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/techhu-gs/cc-discipline/summary"><img src="https://agentmods.dev/badge/skills/techhu-gs/cc-discipline/summary.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.00023 | $0.00571 |
| Opus 5.5 | $0.00009 | $0.00228 |
| Sonnet 5.5 | $0.00005 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
summary 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are about to compact this session. A bad compact loses critical context and degrades work quality. Your job is to write a compact option that preserves what matters most.
What to do
1. Scan current session state
Quickly identify:
- What task(s) are we working on? What's the overall goal?
- What decisions have been made and why?
- What approaches were tried and rejected (and why)?
- What is the current state of implementation? (done / in progress / blocked)
- What are the key constraints and gotchas discovered?
- What are the next steps?
2. Check knowledge files
Read docs/progress.md and docs/todo.md — are they up to date? If not, update them NOW before compacting. They are your primary insurance against context loss: after a compaction the session-start hook re-injects progress.md's Current Status and todo.md's Now list.
Also check: are there unsaved learnings that should go into memory?
3. Write the compact option
Output a compact option string that the user can copy into /compact [option]. The string should:
- Lead with the current task and its status
- Include key decisions with their reasoning (not just the decision)
- Include rejected approaches (so Claude doesn't retry them)
- Include discovered constraints and gotchas
- Include the immediate next steps
- Be specific — "working on auth" is useless, "refactoring OAuth2 token refresh in src/auth/refresh.ts because the current implementation doesn't handle token rotation, decided to use sliding window approach over fixed expiry" is useful
Format:
/compact [your option string here]
Rules
- Be specific, not generic. Every word in the option should carry information that helps post-compact Claude continue at full quality.
- Include the "why", not just the "what". "Using approach A" is less useful than "Using approach A because B had race condition issues we discovered in message #45."
- Include negative knowledge. What NOT to do is as valuable as what to do. "Don't use the built-in cache — it doesn't support TTL, we already tested this."
- Keep it under 500 words. The option needs to be dense, not exhaustive. If you need more, put the details in progress.md and reference it.
- Don't overlap with progress.md or todo.md. The option should complement them, not duplicate them. Focus the option on session-specific context that progress.md might not capture (conversation dynamics, user preferences expressed this session, subtle constraints).
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 Changed a3ac35c409cd
- 2mo ago First seen · 49 lines · 23 tokens per session scan A ccf598d2f3c7
summary is a skill published in the GitHub repository TechHU-GS/cc-discipline (0 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 571 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 skills, from other repositories
ccg-guardian
Use this skill when working on code projects that need memory persistence, code validation, multi-agent coordination, or workflow tracking. Activates Claude Code Guardian MCP tools.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.