What is client-retire?

A client-knowledge archiving workflow for retiring a client. It finds patterns associated with that client, keeps transferable knowledge active, and marks client-specific knowledge as historical.

Use it when a client relationship ends to review, classify, archive, and back up the client's stored patterns.

It preserves useful project knowledge while separating it from information that should no longer be treated as current. It archives items instead of deleting them.

client-retire — Skill for Claude Code by martineserios/thebrana

Install

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.

Any agent

npx skills add martineserios/thebrana --skill client-retire

Clone the repo

git clone --depth 1 https://github.com/martineserios/thebrana

Made for: Claude Code.

Or install brana, the plugin that ships this one along with the rest of its 53 skills, 4 commands, 14 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/martineserios/thebrana/client-retire/github.svg)](https://agentmods.dev/skills/martineserios/thebrana/client-retire)

Your own site

<a href="https://agentmods.dev/skills/martineserios/thebrana/client-retire"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/client-retire/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/martineserios/thebrana/client-retire"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/client-retire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 528 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00028	$0.00528
Opus 5.5	$0.00011	$0.00211
Sonnet 5.5	$0.00006	$0.00106
Haiku 4.5	$0.00003	$0.00053

Measured 1mo ago against content hash 3144aa779363, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

client-retire 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.

system/skills/client-retire/SKILL.md · 58 lines

What it actually says

Client Retire

Identify the client to retire from $ARGUMENTS or current client context.
Primary path (ruflo available):
```
source "$HOME/.claude/scripts/cf-env.sh"
```
Query memory DB for all patterns tagged with this client via cd $HOME && $CF memory search --query "client:{name}". List them with confidence scores.
Fallback path (ruflo unavailable): Read the client's ~/.claude/projects/{project-hash}/memory/MEMORY.md and list all documented patterns.
For each pattern, categorize:
- High-confidence + transferable → keep active, remove client-specific lock
- High-confidence + client-specific → archive with status: historical
- Low-confidence → archive or flag for deletion
Run the archival: tag patterns with archived: true and archived_date: {today}.
Suggest updating ~/.claude/memory/portfolio.md to mark the client as retired.
Never delete anything — only tag and archive. Deletion is a human decision.
Backup knowledge after archiving, via run_knowledge_backup() from ../_shared/backup-knowledge-invoke.md (read that file, extract the BACKUP-KNOWLEDGE-INVOKE-BLOCK, and call it — a non-zero return means the backup failed integrity check; warn the user inline rather than silently continuing, t-2796):
```
run_knowledge_backup
```

Rules

Ask for clarification whenever you need it. If you're unsure which patterns to keep active vs archive, or the client scope is ambiguous — ask. Don't guess.

Changes

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 · 58 lines · 28 tokens per session scan A 3144aa779363

Subscribe to this mod's changes

client-retire is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 528 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-09-03.

Claude Code Memory and context ai-agents ai-development archive claude-code-plugin cleanup client developer-tools historical plugin retire

sw-learn

Captures patterns and learnings from the current work unit. Reviews build failures, gate findings, and architecture decisions. Applies objective promotion criteria autonomously — patterns.md is the artifact.

Obsidian-Owl/specwright · 40 tokens

context-memory

Saves and searches past Claude Code sessions so context, decisions, and code persist across conversations. Use when user says 'remember this', 'save this session', 'recall', 'search past sessions', 'what did we discuss about', or 'find previous work on'. Do NOT use for general file storage, note-taking, or bookmark…

ErebusEnigma/context-memory · 73 tokens

writing-style

Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.

umputun/cc-thingz · 52 tokens

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…

alivecontext/alive · 76 tokens

alive-inbox

Scan 03Inbox/ for unrouted files, present routing suggestions.

alivecontext/alive · 18 tokens

alive-people

Weekly -- cross-reference people mentions, nudge stale contacts.

alivecontext/alive · 15 tokens