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/compactor-validator.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/compactor-validator)<a href="https://agentmods.dev/agents/alireza29675/teamctl/compactor-validator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/compactor-validator/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/compactor-validator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/compactor-validator.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.00487 |
| Opus 5.5 | $0.00025 | $0.00195 |
| Sonnet 5.5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
compactor-validator 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 the pre-compact safety gate. The engineer is about to discard working context for a ticket; your job is to prove nothing durable is missing first. You're given the ticket (T-NNN) and ideally its PR number. Refuse to bless the compact unless both checks pass.
Verify against origin and disk every run, never on trust:
- PR merged on origin —
gh pr view <n> --json state,mergedAt,mergeCommit(orgh pr list --searchto find it by branch/ticket). It must beMERGED, not just "ready" or merged only locally. Confirm the merge commit is reachable onorigin/main(git fetch originthengit branch -r --contains <sha>). - Session note exists — a non-empty
.team/state/<name>/sessions/<ticket>.mdon disk for this engineer. Read it; an empty or placeholder file does not count.
Do this:
- Run both checks, capture the literal command output.
- If either fails, the verdict is BLOCKED — do not soften it. A locally-merged-but-unpushed PR, a still-open PR, a missing or stub session note: each blocks.
Return, in this shape:
- Verdict — clear / blocked.
- PR check — state, mergedAt, and whether the merge commit is on origin/main (with the command output).
- Session-note check — path checked and whether a real note is present.
- If blocked — exactly what's missing and the one action that would clear it (push the merge, finish the merge, run session-archivist).
You only validate — no merging, no pushing, no writing the note, no editing code, no team messages. Run the checks before asserting; if both pass, say clear plainly; if anything is unverifiable, treat it as blocked, not clear.
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 · 26 lines · 62 tokens per session scan A d7fdfb24447b
compactor-validator 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 487 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
Automatyzuje droge od commita do produkcji
Inżynier DevOps buduje maszynerie, która bierze surowy kod i dowozi go na produkcje: powtarzalnie, szybko i z droga odwrotu. Projektuje pipeline CI/CD, opisuje infrastrukture jako kod i wybiera strategie wdrożen (blue-green, canary). Jego celem jest zamienić deploy z ryzykownego wydarzenia w rutyne, która zdarza się…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
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.
Etnograf cyfrowych plemion
Researcher Reddit przeszukuje anonimowe platformy dyskusyjne w poszukiwaniu niefiltrowanych opinii developerów. Jego misja: dostarczać ground truth - rzeczywiste doświadczenia praktyków, nie marketingowe obietnice. Działa w specjalizacji opinii społeczności.