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/lbb00/ai-rules-sync/summarize-sessionnpx skills add lbb00/ai-rules-sync --skill summarize-sessiongit clone --depth 1 https://github.com/lbb00/ai-rules-syncWrote 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/lbb00/ai-rules-sync/summarize-session)<a href="https://agentmods.dev/skills/lbb00/ai-rules-sync/summarize-session"><img src="https://agentmods.dev/badge/skills/lbb00/ai-rules-sync/summarize-session.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00669 |
| Opus 5 | $0.00011 | $0.00334 |
| Sonnet 5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
summarize-session 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Session
Purpose
At the end of a productive coding session, analyze the conversation to extract reusable patterns and generate Claude Code artifacts (rules, skills, commands) that can accelerate future work.
Instructions
-
Review Session Activity
- What problems were solved?
- What code was written or modified?
- What workflows were performed?
- What decisions were made and why?
-
Identify Patterns
Rules Candidates (coding standards, project conventions):
- Repeated code style corrections
- Error patterns that were fixed
- Best practices established
- Project-specific conventions
Skills Candidates (multi-step workflows):
- Complex operations performed multiple times
- Sequences of commands that go together
- Integration or deployment workflows
- Testing or validation procedures
Commands Candidates (single-action shortcuts):
- Frequently used command combinations
- Build/test/deploy shortcuts
- Common git operations
- Project-specific utilities
-
Generate Artifacts
For each identified pattern, create the appropriate artifact:
Rules →
.claude/rules/<name>/RULE.md--- name: rule-name description: Brief description --- # Rule Name ## When to Apply ... ## Guidelines ...Skills →
.claude/skills/<name>/SKILL.md--- name: skill-name description: Brief description --- # Skill Name ## Instructions 1. Step 1 2. Step 2 ...Commands →
.claude/commands/<name>.md# Command Name Description of what this command does. ## Steps 1. ... 2. ... -
Validate Artifacts
- Ensure artifacts are general enough to be reusable
- Remove session-specific details
- Test that instructions are complete and actionable
-
Document Session Summary
- What was accomplished
- What artifacts were generated
- Recommendations for next session
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.
- 3d ago First seen · 135 lines · 22 tokens per session scan A 69ca8d8a115b
summarize-session is a skill published in the GitHub repository lbb00/ai-rules-sync (37 stars, last pushed 14d ago), licensed Unlicense. It adds 22 tokens to every session and 669 once invoked, about $0.0001 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
authoring-skills-and-rules
Author Skills (SKILL.md) and rules/instructions across Claude Code, Cursor, OpenCode, Codex, and GitHub Copilot. Covers frontmatter, file layout, activation model, cross-platform mirroring, and the universal craft: progressive disclosure, trigger-rich descriptions (context pointers), leading words, token budget…
karpathy-guidelines
Tool-agnostic behavioral guidelines for AI coding assistants. Use when writing, reviewing, debugging, or refactoring code to reduce overengineering, surface ambiguity, make surgical changes, and define verifiable success criteria.
spec-driven
Structured planning pipeline with 4 adaptive phases (Specify, Design, Tasks, Execute) and persistent knowledge accumulation for development teams. Auto-sizes depth by complexity from quick fixes to multi-component features. Commands: /explore (understand problem + map context), /plan (write spec → design → tasks)…
skill-memory
Use skill-memory to download, view and edit agent skills in memory. TRIGGER by 'skill', 'memory', 'learn'.
valyu-best-practices
Complete Valyu API toolkit for AI agents. Use this skill when asked to perform real-time search across web, academic, medical, transportation, financial sources, content extraction from URLs, AI-powered answers with citations, or comprehensive deep research reports.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…