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 fatmo666/Caushell --skill session-summarygit clone --depth 1 https://github.com/fatmo666/CaushellWrote 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/fatmo666/caushell/session-summary)<a href="https://agentmods.dev/skills/fatmo666/caushell/session-summary"><img src="https://agentmods.dev/badge/skills/fatmo666/caushell/session-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/fatmo666/caushell/session-summary"><img src="https://agentmods.dev/badge/skills/fatmo666/caushell/session-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.00019 | $0.00057 |
| Opus 5.5 | $0.00008 | $0.00023 |
| Sonnet 5.5 | $0.00004 | $0.00011 |
| Haiku 4.5 | $0.00002 | $0.00006 |
Grade A, and why
session-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.
What it actually says
session-summary
Summarize recent Caushell shell-session findings and point to the persisted
session store used by caushell-claude.
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 · 10 lines · 19 tokens per session scan A 52e3ecaecfeb
session-summary is a skill published in the GitHub repository fatmo666/Caushell (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 57 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
recall-promote
Use when recurring themes need promotion to permanent MEMORY.md entries, or when the user mentions 'promote', 'recurrence', or 'recurring themes'.
progress
Use when the user wants to view their current progress.md file. Also use when the user mentions 'show progress', 'current progress', 'what have we done', or '/tandem:progress'.
memory
Use when the user wants to view their current MEMORY.md file. Also use when the user mentions 'show memory', 'current memory', 'what do we know', or '/tandem:memory'.
handoff
Write a short handoff note for the next chat or a teammate, with what is done, what is open, what comes next and what was rejected and why. Saves it to project memory so the next chat sees it at the start, and prints it so it can be pasted into a message or a pull request. Use when the user ends a piece of work…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
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…