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 learngit 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/learn)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/learn"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/learn/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/learn"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/learn.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.00069 | $0.03286 |
| Opus 5 | $0.00034 | $0.01643 |
| Sonnet 5 | $0.00014 | $0.00657 |
| Haiku 4.5 | $0.00007 | $0.00329 |
Grade A, and why
learn 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)
You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.
Capture Learning
Save a development learning (bug, workaround, pattern, config, pitfall, architecture decision, tool behavior) to persistent memory so it's available in future sessions.
Working Directories
- Vault (source of truth):
__VAULT_ROOT__, ALL detailed learnings go here - Memory directory (auto-memory): the path provided by the system prompt's auto memory section (derived from vault path:
$HOME/.claude/projects/-<vault-path-sanitized>/memory/). Contains ONLY two files:MEMORY.md, thin index with pointers to vault filespitfalls.md, one-liner gotchas (exception: stays in memory for fast loading)
- Codebase:
__CODEBASE_ROOT__
CRITICAL RULES:
- NEVER create any file in the memory directory besides
MEMORY.mdandpitfalls.md. Nofeedback_*.md,project_*.md,reference_*.md, or any other.mdfiles - ALL detailed content goes to the vault and is referenced from
MEMORY.md - When writing to
MEMORY.mdorpitfalls.md, use the memory directory path from the auto memory system (shown in system prompt). Do NOT guess or use wildcards
Phase 0: Detect Learnings
If $ARGUMENTS is provided
Use it as the learning description. Skip to Phase 1.
If invoked without arguments (after /debug-mode, /feature-dev, or conversation)
Scan the recent conversation context for learnable moments:
- Bug root causes that were confirmed with evidence
- Unexpected behaviors that took investigation to understand
- Config or env var discoveries (ports, commands, compatibility)
- Workarounds applied for known issues
- Patterns that worked well and should be reused
- Tool/CLI behaviors that surprised or blocked progress
- Architecture decisions with rationale worth preserving
Present candidates:
Learnings detected in this session:
1. [BUG] svc-experiences TypeORM silently ignores WHERE on nullable columns
Impact: HIGH | Service: svc-experiences
2. [CONFIG] BigQuery ADC requires gcloud auth before local dev
Impact: MEDIUM | Service: svc-experiences
3. [PATTERN] Bulk upsert with ON CONFLICT needs explicit column list
Impact: MEDIUM | Service: svc-experiences
Save all? Or pick by number (e.g., 1,3)?
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 · 349 lines · 69 tokens per session scan A 069031cdeaa7
learn is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 3,286 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-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/.
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'.
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.
memorix-sessions
Use when resuming work, preparing handoff context, binding an HTTP control-plane project, or deciding whether sessionstart is useful.
memory-processor
Iva's daily-memory processor. Reads the day's two-sided transcript (daily/YYYY-MM-DD.md), distills noteworthy entities / decisions / ideas into typed autograph cards, links them into the graph, and produces a daily-summary card (topics + MOC) that navigates down to the raw transcript and up to the week. Model-agnostic…