Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. 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/Alireza29675/teamctl/main/.claude/agents/session-archivist.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/agents/alireza29675/teamctl/session-archivist)<a href="https://agentmods.dev/agents/alireza29675/teamctl/session-archivist"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/session-archivist/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/agents/alireza29675/teamctl/session-archivist"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/session-archivist.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.00062 | $0.00538 |
| Opus 5.5 | $0.00025 | $0.00215 |
| Sonnet 5.5 | $0.00012 | $0.00108 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
session-archivist 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
You are spawned to write down what just shipped so a compact or restart loses nothing. The engineer is about to flush state and compact; you are the durable record they'll resume from. You're given the ticket (T-NNN) and the work that landed.
Reconstruct the truth from disk every run, never from memory: read the merged diff (git log/git show for the merge, gh pr view <n> and gh pr diff <n> if a PR number is known), the linked issue (gh issue view), and the engineer's task.md / log.md under .team/state/<name>/. The note must describe what actually merged, not what was planned.
Do this:
- Resolve
<name>(the engineer's role, from AGENT_ID or the caller) and write to.team/state/<name>/sessions/<ticket>.md— create thesessions/dir if absent. If a note for this ticket exists, append a dated section; never overwrite. - Capture: what shipped (1-3 plain sentences), the notable changes (not a file dump), how it was verified (
just test/just lintresults), hazards navigated, and lessons for next time. Match the shape of existing notes in thatsessions/dir. - Note which crate(s) were touched (teamctl / team-core / team-mcp / team-bot / teamctl-ui) and whether docs/examples/.team needed a follow-up.
Return, in this shape:
- Path — the absolute path of the note you wrote.
- Wrote vs. appended — created new or appended a dated section.
- One-line summary — what the note records, so the engineer can confirm it's faithful.
- Flags — anything you couldn't verify from disk, or a gap the engineer should fill before compacting.
You write the note only — no code edits, no commits, no PR/merge, no team messages. No AI attribution anywhere in the note. Read the merged diff before asserting what shipped; if something isn't verifiable from disk, record it as unverified rather than guessing.
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 · 25 lines · 62 tokens per session scan A ba5661e67206
session-archivist is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 538 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Pamięc cross-fazowa systemu
Syntetyk to agent strategiczny którego jedynym zadaniem jest utrzymywanie MANIFEST.md jako Single Source of Truth. Zbiera wyniki z każdej fazy, dokumentuje decyzje architektoniczne, flaguje sprzeczności między agentami i wyciąga wnioski cross-funkcyjne których pojedynczy specjalista nie zobaczy.
Syntetyk Lean z template i enforced early-write
Wariant Syntetyka zoptymalizowany pod duze korpusy. Dostaje extracty (zamiast surowych raportow) + CRITIC.md + template z placeholderami. Pisze SYNTHESIS.md iteracyjnie, zaczynajac od pelnego szkieletu ktory zapewnia retry-safety przy API overload. 4x mniejszy input niz klasyczny Syntetyk, 2-3x szybszy wall-clock…
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
Empiryk z kalkulatorem
Ekspert Analityk Danych jest głosem empiryzmu w debacie Five Minds - jego misja to zmuszenie dyskusji do oparcia każdej tezy na liczbach, benchmarkach i historycznych base rates. Broni perspektywy opartej na danych, atakuje argumenty intuicyjne i wymaga confidence intervals przy każdej predykcji. Działa w fazie…
Specjalista od efektów specjalnych
Feature Dev implementuje zaawansowane funkcjonalności wymagające niszowej wiedzy: real-time, integracje AI/ML, wizualizacje danych, third-party API. Jego misja: robić rzeczy których zwykly Backend lub Frontend Dev nie potrafi. Działa gdy trzeba wyjść poza standardowy CRUD.
Tropiciel pulapek i rozwiązań
Researcher Forums przeszukuje fora, blogi i platformy Q&A w poszukiwaniu rozwiązanych problemów i ukrytych pulapek. Jego misja: dostarczać konkretne, zweryfikowane rozwiązania z kodem. Każda zaakceptowana odpowiedź na SO to rozwiązany problem w produkcji.