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 wigtn/wigtn-plugins --skill team-memory-protocolgit clone --depth 1 https://github.com/wigtn/wigtn-pluginsWrote 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/wigtn/wigtn-plugins/team-memory-protocol)<a href="https://agentmods.dev/skills/wigtn/wigtn-plugins/team-memory-protocol"><img src="https://agentmods.dev/badge/skills/wigtn/wigtn-plugins/team-memory-protocol/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/wigtn/wigtn-plugins/team-memory-protocol"><img src="https://agentmods.dev/badge/skills/wigtn/wigtn-plugins/team-memory-protocol.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.02024 |
| Opus 5.5 | $0.00017 | $0.00810 |
| Sonnet 5.5 | $0.00008 | $0.00405 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
team-memory-protocol 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Memory Protocol
팀 기반 병렬 빌드에서 팀 간 데이터 공유를 위한 3계층 메모리 관리 프로토콜입니다.
3-Layer Memory Architecture
┌─────────────────────────────────────────────────────────────┐
│ 3계층 공유 메모리 구조 │
├─────────────────────────────────────────────────────────────┤
│ │
│ Layer 1: Auto Memory (MEMORY.md) │
│ ├── 지속성: 세션 간 영구 지속 │
│ ├── 용도: 프로젝트 컨벤션, 패턴, 아키텍처 결정 │
│ ├── 읽기: 빌드 시작 시 (모든 팀) │
│ └── 쓰기: 빌드 완료 후 (Coordinator만) │
│ │
│ Layer 2: SHARED_CONTEXT (파일 기반) │
│ ├── 지속성: 빌드 세션 동안 (완료 후 참조용 유지) │
│ ├── 용도: API 계약, 공유 타입, 환경변수, 진행 상태 │
│ ├── 읽기: 빌드 중 (모든 팀) │
│ └── 쓰기: Coordinator + Backend 팀만 │
│ │
│ Layer 3: PLAN 원장 (docs/todo_plan/PLAN_{feature}.md) │
│ ├── 지속성: 파일 — 세션이 끝나도 남는다 │
│ ├── 용도: 팀별 진행 추적, 의존성 관리 │
│ ├── 읽기: 모든 팀 / 쓰기: Coordinator │
│ └── 형식: `- [ ]` 체크박스 + blocked-by 주석 │
│ │
└─────────────────────────────────────────────────────────────┘
SHARED_CONTEXT 파일 관리
파일 경로
docs/shared/SHARED_CONTEXT_{feature_name}.md
생성 템플릿
# SHARED_CONTEXT: {feature_name}
> team-build-coordinator 자동 생성. 팀 간 조율용.
> 생성일: {timestamp}
> 기능: {feature_name}
## API Contract
| Method | Path | Request Type | Response Type | Owner |
|--------|------|-------------|--------------|-------|
## Shared Types
<!-- TypeScript interfaces/types 공유 -->
<!-- Backend 팀이 정의, 다른 팀이 import하여 사용 -->
## Environment Variables
| Variable | Required By | Description |
|----------|------------|-------------|
## Integration Points
| From | To | Type | Description |
|------|-----|------|-------------|
## Team Progress
| Team | Status | Tasks | Completion | Last Update |
|------|--------|-------|------------|-------------|
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 · 229 lines · 42 tokens per session scan A 327beb73e3dd
team-memory-protocol is a skill published in the GitHub repository wigtn/wigtn-plugins (45 stars, last pushed 4d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,024 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 skills, from other repositories
relay
A Chinese-language procedure for handing an unfinished task from one AI session to another without losing its context.
doc-digest
Turn a long document, PDF, transcript, spreadsheet or log into a compact working digest the conversation can continue from. Use when the user shares or pastes something long (several pages or more) and wants to discuss, analyze, compare or use it over more than one message, or asks to summarize a document so they can…
fresh-start
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
token-check
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window and usage limits, and how to cut it. Use when the user asks how big something is in tokens, why they keep hitting limits, or whether a file is too large to send.
project-context
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the same thing, or asks how to set up a…
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.