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 mizukaizen/hive-doctrine-mcp --skill client-onboardinggit clone --depth 1 https://github.com/mizukaizen/hive-doctrine-mcpWrote 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/mizukaizen/hive-doctrine-mcp/client-onboarding)<a href="https://agentmods.dev/skills/mizukaizen/hive-doctrine-mcp/client-onboarding"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/client-onboarding/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/mizukaizen/hive-doctrine-mcp/client-onboarding"><img src="https://agentmods.dev/badge/skills/mizukaizen/hive-doctrine-mcp/client-onboarding.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.00000 | $0.00486 |
| Opus 5 | $0.00000 | $0.00243 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
client-onboarding 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Client Onboarding
Use when onboarding a new client. Creates a structured onboarding process that captures requirements, sets expectations, and establishes communication norms.
Trigger
Invoke this skill when a new client engagement begins, after the contract is signed but before development starts.
Process
1. Requirements Gathering
Walk through a structured questionnaire:
Business Context:
- What problem does this project solve for your business?
- Who are the end users? How many?
- What does success look like? How will you measure it?
- Are there hard deadlines (e.g., event launch, regulatory compliance)?
Technical Requirements:
- Existing systems this must integrate with?
- Preferred tech stack or platform constraints?
- Expected traffic/load (users, requests per second)?
- Data sensitivity level (public, internal, PII, financial)?
Design Requirements:
- Brand guidelines or design system?
- Reference sites or apps you admire?
- Accessibility requirements (WCAG level)?
Process Preferences:
- Preferred communication channel (email, Slack, Teams)?
- Feedback turnaround time expectation?
- Approval process (single stakeholder or committee)?
- How often do you want status updates?
2. Scope Agreement
Based on requirements, draft a scope document covering:
- Included features (explicit list)
- Excluded features (explicit list — prevents future disputes)
- Assumptions (what must be true for estimates to hold)
- Change request process
3. Project Setup
Run /new-client to scaffold the project structure with gathered information.
4. Kickoff Checklist
Generate a kickoff checklist:
- Requirements document reviewed and signed off
- Scope document reviewed and signed off
- Communication channel set up
- Access to client systems granted (staging, APIs, brand assets)
- First milestone and deadline agreed
- Status update schedule confirmed
Output
Save onboarding artefacts to clients/[client-slug]/docs/onboarding/:
requirements.md— Captured requirementskickoff-checklist.md— Checklist with status
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 · 67 lines · 0 tokens per session scan A d1c6e53f20fc
client-onboarding is a skill published in the GitHub repository mizukaizen/hive-doctrine-mcp (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 486 tokens. 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
writbase-recipes
WritBase API recipes reference (internal).
extract-tasks
Review conversation and extract untracked work items as WritBase tasks (writbase:info, writbase:addtask). Use at end of session to capture untracked work.
loop
Poll WritBase for top tasks and work through them autonomously. Use when you want to process the task queue, auto-work, or run the work loop.
writbase-router
Route task, writbase, agent, permission, provenance, webhook, and delegation requests to WritBase MCP tools. Triggers on keywords like task, writbase, work, assign, delegate, permission, audit, webhook, subscribe, provenance, agent key.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
meeting-to-deal
Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…