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 Hadi99K/AGENT_SKILLS --skill team-summarygit clone --depth 1 https://github.com/Hadi99K/AGENT_SKILLSWrote 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/hadi99k/agent_skills/team-summary)<a href="https://agentmods.dev/skills/hadi99k/agent_skills/team-summary"><img src="https://agentmods.dev/badge/skills/hadi99k/agent_skills/team-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/hadi99k/agent_skills/team-summary"><img src="https://agentmods.dev/badge/skills/hadi99k/agent_skills/team-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.00057 | $0.01617 |
| Opus 5.5 | $0.00023 | $0.00647 |
| Sonnet 5.5 | $0.00011 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
team-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 4d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
👥 Team Member Summaries & Activity Log (team-summary)
What I Do
- Manage
TEAM_SUMMARY.md: Creates and maintains a dedicated team activity file where each team member (human developer, collaborator, or specialized AI agent) has their own designated summary section. - Isolate Individual Contributions: Ensures team members update only their own work log, preventing team members or AI agents from accidentally erasing or overwriting each other's progress notes.
- Track Asynchronous Standups: Provides clear visibility into:
- What each person/agent recently built or fixed.
- Which files they touched or currently own.
- What they are actively working on next.
- Any blockers or cross-member dependencies.
- Maintain a Team Roster: Keeps an at-a-glance status table at the top of the file so anyone entering the project immediately knows who is working on what.
When to Use Me
- When multiple developers, contributors, or AI agent sessions work on the same project.
- After finishing a task or feature sprint to record what you (or your agent persona) accomplished.
- When starting work to announce your active focus and prevent duplicate effort.
- When the user asks: "update my team summary", "log what I did in the team file", "add member summary", or "create TEAM_SUMMARY.md".
🏛️ Structure of TEAM_SUMMARY.md
The file is organized with a quick high-level roster followed by self-contained member sections:
┌─────────────────────────────────────────────────────────────┐
│ TEAM_SUMMARY.md (or TEAM_LOG.md) │
├─────────────────────────────────────────────────────────────┤
│ 📌 Team Roster & Quick Status (At-a-glance table) │
├─────────────────────────────────────────────────────────────┤
│ 👤 Member: [Member A / Agent Persona 1] │
│ - Role & Last Active │
│ - 🎯 Current Focus & Next Steps │
│ - ✅ Recent Accomplishments (Dated logs) │
│ - 📂 Key Files Touched / Owned │
│ - 🚧 Blockers & Notes for Team │
├─────────────────────────────────────────────────────────────┤
│ 👤 Member: [Member B / Agent Persona 2] │
│ - ... (Dedicated, isolated section) │
└─────────────────────────────────────────────────────────────┘
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.
- 4d ago First seen · 158 lines · 57 tokens per session scan A c0834b858eee
team-summary is a skill published in the GitHub repository Hadi99K/AGENT_SKILLS (3 stars, last pushed 4d ago), licensed MIT. It adds 57 tokens to every session and 1,617 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-10-18.
Other skills, from other repositories
openspec-bulk-archive-change
Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".
knowledge-curation
Context priming before work (bd prime) and self-reflection after completion to extract patterns, gotchas, and decisions into the knowledge base.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
bridge
Capture a cross-project connection the moment it surfaces, such as a shared pattern, a person carrying context between projects, a story that lends another project credibility, a feedback loop. Use when one project feeds, reuses, reinforces another: 'connects to', 'feeds into', 'same pattern as'. Writes one YAML file…
stash
Stash session context [name].