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 arozumenko/sdlc-skills --skill gathering-contextgit clone --depth 1 https://github.com/arozumenko/sdlc-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/arozumenko/sdlc-skills/gathering-context)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/gathering-context"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/gathering-context/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/arozumenko/sdlc-skills/gathering-context"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/gathering-context.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.00059 | $0.00645 |
| Opus 5 | $0.00030 | $0.00322 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
gathering-context 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context Gatherer
Find prior discussions, decisions, and commitments across channels — fast. Walk channels in cost order and stop early when you have enough.
Inputs
- Person — name or email
- Topic — short phrase
- Time window — default: last 2 weeks. Widen only if the topic clearly demands history.
Search Order (fast → slow)
1. Local knowledge base
- If a local index exists (e.g.
.knowledge/threads.json),Readit andGrepfor the person's email and topic keywords. - This gives pre-summarized threads — usually enough on its own for routine asks.
2. Email
search-querywithfrom:<email> AND <keywords>(andto:<email>variant).- Fall back to
list-mail-messages+ manual filter ifsearch-queryis unavailable. - Pull bodies with
get-mail-messageonly for the top 3–5 hits — never bulk-read.
3. Teams chats
find-chatby name →list-chat-messagesfor the matched chats with recent activity.- Aggregate consecutive messages from the same sender within ~2 minutes into one turn before summarizing — people fragment messages and raw dumps are noisy.
4. Web (only if needed)
tavily_searchfor public topics (announcements, vendor docs). Never web-search internal/private topics.
Stop as soon as you have enough to answer the question. Don't exhaust every channel by default.
Output
Max ~500 words. Facts, not essays.
## Context for <person> — <topic>
### Prior conversations
- [date] <channel>: <one-line summary>
- [date] <channel>: <one-line summary>
### Decisions & commitments
- <what was agreed, by whom, when>
### Related discussions
- <relevant context from other people/threads>
### Open items
- <anything unresolved or pending>
If nothing relevant exists, say so in one line. Never fabricate context.
Rules
- Default window: last 2 weeks. Widen only with explicit need.
- Summarize — never paste raw email bodies or message dumps.
- Mask PII / credentials encountered in searches.
- If channels disagree, flag the conflict rather than picking a side.
- Aggregate Teams message bursts before summarizing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 72 lines · 59 tokens per session scan A ac7f90bbdda8
gathering-context is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 645 once invoked, about $0.0003 per session on Opus 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.