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 fzfclee/consulting-skills --skill service-blueprintgit clone --depth 1 https://github.com/fzfclee/consulting-skillsWrote 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/fzfclee/consulting-skills/service-blueprint)<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/service-blueprint"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/service-blueprint/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/fzfclee/consulting-skills/service-blueprint"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/service-blueprint.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.00048 | $0.00778 |
| Opus 5 | $0.00024 | $0.00389 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
service-blueprint 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Service Blueprint
Use this skill to run Service Blueprint as a practical consulting method, not as a generic framework explanation.
Method Notes
- Start from a specific customer journey.
- Map customer actions, frontstage, backstage, support processes, systems, and evidence.
Required Inputs
Collect or infer these inputs before execution:
- service scope
- customer journey
- roles
- systems and process evidence
If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.
When Not To Use
Do not use when the service boundary and customer scenario are undefined or when backstage activities would have to be invented from a frontstage complaint. Mark missing customer and process evidence explicitly.
Adjacent Methods
user-journey-mapping: user experience without backstage operations.jobs-to-be-done: demand and switching logic.empathy-map: perceptions of one actor.
Step-by-Step Execution
| Step | Required input | How to execute | Output |
|---|---|---|---|
| Select service scenario | Customer journey, service scope, user goal. | Choose one journey scenario and outcome. | Blueprint scope. |
| Map customer actions | Journey stages and touchpoints. | Write customer-visible actions in sequence. | Customer action row. |
| Map frontstage and evidence | People, channels, scripts, forms, physical/digital evidence. | Add visible service interactions and artifacts. | Frontstage/evidence rows. |
| Map backstage and support | Internal teams, systems, policies, handoffs. | Add backstage work, support processes, systems, and dependencies. | Backstage/support rows. |
| Diagnose failures | Completed blueprint. | Identify handoff gaps, wait states, rework, missing ownership, and system constraints. | Service improvement plan. |
Output Template
### 1. Service Scope
Customer / segment:
Journey start / end:
Service outcome:
Evidence:
### 2. Blueprint
| Stage | Customer action | Frontstage | Evidence | Backstage | Support system |
|---|---|---|---|---|---|
| | | | | | |
### 3. Failures And Handoffs
| Point | Failure / delay | Cause | Owner | Customer impact |
|---|---|---|---|---|
| | | | | |
### 4. Improvement Plan
| Intervention | Owner | Timing | Service signal | Guardrail |
|---|---|---|---|---|
| | | | | |
### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:
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.
- 11d ago First seen · 87 lines · 48 tokens per session scan A 6e7e98d1f4f4
service-blueprint is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 23d ago), licensed Apache-2.0. It adds 48 tokens to every session and 778 once invoked, about $0.0002 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
ppt-keynote
An operating-model redesign for a scaling logistics firm — the diagnosis, the target model, and the transition roadmap. Built as a decision-grade consulting deck for client sponsor, ops leaders.
belbin-team-roles
Analyzes team composition using Belbin's nine team roles across Thinking, Action, and People categories. Maps team members to roles such as Plant, Shaper, Coordinator, Implementer, and others to identify gaps, overlaps, and imbalances. Use when hiring to fill role gaps, diagnosing recurring team conflicts, auditing…
doblin-ten-types
Maps and designs innovation strategy using Doblin's Ten Types of Innovation across Configuration (Profit Model, Network, Structure, Process), Offering (Product Performance, Product System), and Experience (Service, Channel, Brand, Customer Engagement). Use when auditing current innovation profile, identifying…
grow-model
Facilitates coaching conversations and structured decision-making using Whitmore's GROW model: Goal (clarify objectives), Reality (assess current state honestly), Options (generate alternatives), and Will (commit to action). Use when coaching team members, making strategic decisions as a founder, breaking through…
hackman-enabling-conditions
Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance…
myers-briggs-type-indicator
Maps team cognitive diversity using the MBTI four-dichotomy personality framework: Extraversion/Introversion, Sensing/Intuition, Thinking/Feeling, Judging/Perceiving. Use when diagnosing co-founder communication friction, designing cognitively diverse teams, adapting communication style for different audiences…