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 team-attention/plugins-for-claude-natives --skill session-wrapgit clone --depth 1 https://github.com/team-attention/plugins-for-claude-nativesWrote 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/team-attention/plugins-for-claude-natives/session-wrap)<a href="https://agentmods.dev/skills/team-attention/plugins-for-claude-natives/session-wrap"><img src="https://agentmods.dev/badge/skills/team-attention/plugins-for-claude-natives/session-wrap.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.01213 |
| Opus 5 | $0.00026 | $0.00607 |
| Sonnet 5 | $0.00010 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00121 |
Grade A, and why
session-wrap 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 8d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Wrap Skill
Comprehensive session wrap-up workflow with multi-agent analysis.
Execution Flow
┌─────────────────────────────────────────────────────┐
│ 1. Check Git Status │
├─────────────────────────────────────────────────────┤
│ 2. Phase 1: 4 Analysis Agents (Parallel) │
│ ┌─────────────────┬─────────────────┐ │
│ │ doc-updater │ automation- │ │
│ │ (docs update) │ scout │ │
│ ├─────────────────┼─────────────────┤ │
│ │ learning- │ followup- │ │
│ │ extractor │ suggester │ │
│ └─────────────────┴─────────────────┘ │
├─────────────────────────────────────────────────────┤
│ 3. Phase 2: Validation Agent (Sequential) │
│ ┌───────────────────────────────────┐ │
│ │ duplicate-checker │ │
│ │ (Validate Phase 1 proposals) │ │
│ └───────────────────────────────────┘ │
├─────────────────────────────────────────────────────┤
│ 4. Integrate Results & AskUserQuestion │
├─────────────────────────────────────────────────────┤
│ 5. Execute Selected Actions │
└─────────────────────────────────────────────────────┘
Step 1: Check Git Status
git status --short
git diff --stat HEAD~3 2>/dev/null || git diff --stat
Step 2: Phase 1 - Analysis Agents (Parallel)
Execute 4 agents in parallel (single message with 4 Task calls).
Session Summary (Provide to all agents)
Session Summary:
- Work: [Main tasks performed in session]
- Files: [Created/modified files]
- Decisions: [Key decisions made]
Parallel Execution
Task(
subagent_type="doc-updater",
description="Document update analysis",
prompt="[Session Summary]\n\nAnalyze if CLAUDE.md, context.md need updates."
)
Task(
subagent_type="automation-scout",
description="Automation pattern analysis",
prompt="[Session Summary]\n\nAnalyze repetitive patterns or automation opportunities."
)
Task(
subagent_type="learning-extractor",
description="Learning points extraction",
prompt="[Session Summary]\n\nExtract learnings, mistakes, and new discoveries."
)
Task(
subagent_type="followup-suggester",
description="Follow-up task suggestions",
prompt="[Session Summary]\n\nSuggest incomplete tasks and next session priorities."
)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 186 lines · 52 tokens per session scan A 7e7e032cc80c
session-wrap is a skill published in the GitHub repository team-attention/plugins-for-claude-natives (824 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,213 once invoked, about $0.0003 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
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…