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 ThomasMoreAI/legal-skills-open --skill cold-start-interview-banking-fintech-legal-bossmann007git clone --depth 1 https://github.com/ThomasMoreAI/legal-skills-openWrote 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/thomasmoreai/legal-skills-open/cold-start-interview-banking-fintech-legal-bossmann007)<a href="https://agentmods.dev/skills/thomasmoreai/legal-skills-open/cold-start-interview-banking-fintech-legal-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cold-start-interview-banking-fintech-legal-bossmann007/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/thomasmoreai/legal-skills-open/cold-start-interview-banking-fintech-legal-bossmann007"><img src="https://agentmods.dev/badge/skills/thomasmoreai/legal-skills-open/cold-start-interview-banking-fintech-legal-bossmann007.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.00067 | $0.00674 |
| Opus 5.5 | $0.00027 | $0.00270 |
| Sonnet 5.5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
cold-start-interview-banking-fintech-legal-bossmann007 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 24d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cold Start: Banking & Fintech Legal Practice Interview
Purpose
Your first time using this plugin, it interviews you conversationally (no forms, no jargon) to learn your practice — how your team is structured, what products you handle, which regulators matter, where the risk ceiling is. Once. Then every skill in this plugin reads that profile before doing work.
If you're re-running (you've onboarded new people or shifted product focus), pass --redo to re-interview.
The interview
This is a conversation, not a survey. I'll ask ~5-8 open questions. Your answers populate ~/.claude/plugins/config/claude-for-legal/banking-fintech-legal/CLAUDE.md — a living document you edit directly when things change. You don't fill out a form; you tell me how your team actually works.
I'll ask about:
- Your organization — name, type (banco, fintech, exchange, custody, etc.), size, who's the GC/lead counsel
- What you do — products (credit, payments, Pix, crypto, staking, etc.), customer segments (retail, corporate, etc.)
- Regulators — who watches you (BCB, CVM, ANPD, others)
- Risk appetite — what thresholds trigger escalation, what's automatic to the GC
- The thing that hurts — in your own words, what's the worst problem that lands on your desk
That's it. Your answers feed the playbook sections in CLAUDE.md — interest caps, VASP classification rules, Open Finance consent models, etc. When you don't have a position on something yet, that stays blank in the template; skills will ask you to fill it in as needed.
What you get
After the interview:
- CLAUDE.md populated with your team profile, risk appetite, and skeleton playbook. Not comprehensive — meant to be filled in as you work.
- Each skill knows your context — when you run
/banking-fintech-legal:payment-institution-compliance, it doesn't ask "what type of institution are you" because it already read CLAUDE.md. - Edited, not auto-filled. The document is yours. Change a threshold? Edit the file. No re-interview needed.
What ships with it
2 files 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.
- 24d ago First seen · 48 lines · 67 tokens per session scan A 76f54558a69d
cold-start-interview-banking-fintech-legal-bossmann007 is a skill published in the GitHub repository ThomasMoreAI/legal-skills-open (95 stars, last pushed 15d ago), licensed Apache-2.0. It adds 67 tokens to every session and 674 once invoked, about $0.0003 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-04.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…