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 ivanhoinacki/team-exp-claude-config --skill capture-knowledgegit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/capture-knowledge)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/capture-knowledge"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/capture-knowledge/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/ivanhoinacki/team-exp-claude-config/capture-knowledge"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/capture-knowledge.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.00099 | $0.03468 |
| Opus 5 | $0.00049 | $0.01734 |
| Sonnet 5 | $0.00020 | $0.00694 |
| Haiku 4.5 | $0.00010 | $0.00347 |
Grade A, and why
capture-knowledge 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 9d 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 — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Knowledge from Discussions
Phase 0: Vault RAG (MANDATORY)
Before ANY file reads, grep, or codebase exploration, call query_vault with relevant keywords and service_filter. This is non-negotiable. The vault contains pitfalls, business rules, review learnings, and patterns that prevent rework. Skip = rework.
Extract business rules, technical flows, and domain knowledge from Slack. Save as structured knowledge that informs future development decisions.
Two Modes
Mode 1: Single Thread (/capture-knowledge <URL>)
Captures one specific Slack thread. Use when someone shares a URL or you spot an interesting discussion.
Mode 2: Channel Sweep (/capture-knowledge sweep)
Scans entire channels for Q&A threads with valuable knowledge. Launches parallel agents per channel. Use weekly to keep the KB updated.
Arguments:
sweeporsweep all= scan Tier 1 + Tier 2 channelssweep tier1= scan only Tier 1 (Team & Core)sweep tier2= scan only Tier 2 (Adjacent Teams)sweep tier3= scan only Tier 3 (Provider Integrations)sweep #channel-name= scan one specific channel
Vertical Context (applies to ALL modes)
Our team (TEAM_VERTICALS) owns:
- Backend: svc-experiences, svc-ee-offer, svc-car-hire, svc-addons, svc-tag, svc-occasions, svc-fx, svc-traveller
- Frontend: www-ee-admin, www-ee-customer, www-ee-vendor
- Providers: LED/Salesforce (svc-ee-offer), Rezdy, Klook, Derbysoft, Collinson, CustomLinc/South Sea Cruises
- Key flows: experience booking, complimentary experiences (bundled with hotels), refunds, promo distribution, provider sync, availability, checkout traveller forms, search indexing
- Terminology: "LED" = "Lux Everyday" = svc-ee-offer = Salesforce Connect. "Complimentary" = "bundle" (in Slack). "TTD" = "things to do" = experiences
When capturing knowledge, always evaluate through the lens of our vertical. Even in other team's channels, only capture what is relevant to TEAM_VERTICALS.
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.
- 9d ago First seen · 335 lines · 99 tokens per session scan A cc1fc80fa174
capture-knowledge is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 3,468 once invoked, about $0.0005 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-31.
Other skills, from other repositories
me-card
Render the user's saved /.me/ context as a single ASCII-art infographic card. Use when the user asks to "show my info", "print my card", "render my profile", "me card", "ascii infographic of my dot-me", or invokes the /me-card shortcut. Read-only — never writes to /.me/.
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
mempalace-recall
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall…
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.