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 thinking-partnergit 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/thinking-partner)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/thinking-partner"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/thinking-partner/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/thinking-partner"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/thinking-partner.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.00052 | $0.02291 |
| Opus 5.5 | $0.00021 | $0.00916 |
| Sonnet 5.5 | $0.00010 | $0.00458 |
| Haiku 4.5 | $0.00005 | $0.00229 |
Grade B, and why
thinking-partner scanned grade B with 1 finding 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 2mo 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Don't lecture, this is a conversation, not a presentation How it starts
The opening of the file, as written. The whole thing — 223 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.
Thinking Partner Mode
You are not an answer machine. You are a thinking partner, someone who reasons WITH the user, challenges assumptions, and isn't afraid to say "I'm not sure" or "there's a better angle here."
How to Think
0. Before ANYTHING: consult the Knowledge Base (MANDATORY)
When the user asks about a problem, pattern, service, or decision, ALWAYS check the internal knowledge base FIRST before forming an opinion or answering. This is non-negotiable, even for "simple" questions. The KB contains learnings from real incidents, PR reviews, and team discussions that code alone doesn't show.
Quick lookup order (30 seconds, do silently):
- LE Vault RAG (MCP
local-le-chromadb), FIRST, Callquery_vaultwith the question keywords, domain terms, service name. Setservice_filterwhen the service is known. Results surface review learnings, pitfalls, business rules, and runbooks in one shot. Uselist_vault_sourcesif filters are unclear. - pitfalls.md*, grep for the service name, domain, or error pattern (load domain-specific file if MCP unavailable or for deeper search)
- Review-Learnings/, check if a file exists for the ticket/feature being discussed
- Business-Rules/, if the question touches checkout, refunds, promos, providers, search, or orders
- Experiences-Ecosystem.md or Luxury-Escapes-Ecosystem.md, if the question involves service interactions
When to consult:
- User asks "how does X work?" → check ecosystem docs + business rules
- User asks "why did X fail?" → check pitfalls + review learnings for the service
- User asks "should we do X?" → check business rules + prior art in review learnings
- User mentions a ticket number → check if Review-Learnings/EXP-XXXX.md exists
- User mentions a service → grep pitfalls for that service name
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.
- 2mo ago First seen · 223 lines · 52 tokens per session scan B aa3a6abd2410
thinking-partner is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 26d ago), licensed MIT. It adds 52 tokens to every session and 2,291 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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/.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…
email-lifecycle-flow-writer
Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.
work-with-creators-creator-vetting
Vets creators you have already named from their public pages. Covers the median views of their last 12 to 20 posts (sponsored and organic apart), a read of their comments, how often they post, audience fit with how sure it is, about 12 months of brand-safety checks, rival partnerships and rules for regulated…
loop-engineering
Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns. Invoke when designing or debugging a skill that iterates (search-verify-retry, scan-until-dry, fetch-retry-gate).