service-check

service-check is a skill for Claude Code from haabe/mycelium. It costs 21 tokens per session (1,657 once invoked), scanned A, original, MIT.

A checklist for judging a service or feature against 15 principles of good service design. It checks whether people can find it, understand it, use it, and finish their task without unnecessary barriers.

In plain words
What is it for?
Use it to review a service or feature and mark each principle as pass, partial, fail, or not applicable.
Why use it?
It exposes usability problems that may be hidden when a team evaluates only whether a feature technically works. It also checks that the service does not require specialist knowledge or knowledge of internal teams.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: mentions CLAUDE.md.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the mycelium plugin — 61 skills, 6 hooks shipped together

Good fit Use it to review a service or feature and mark each principle as pass, partial, fail, or not applicable.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add haabe/mycelium
Claude Code
/plugin install mycelium

Made for: Claude Code.

Or install mycelium, the plugin that ships this one along with the rest of its 61 skills, 6 hooks.

Wrote 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.

agentmods badge for service-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/haabe/mycelium/service-check.svg)](https://agentmods.dev/skills/haabe/mycelium/service-check)
Your own site
<a href="https://agentmods.dev/skills/haabe/mycelium/service-check"><img src="https://agentmods.dev/badge/skills/haabe/mycelium/service-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,657 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.01657
Opus 5 $0.00010 $0.00829
Sonnet 5 $0.00004 $0.00331
Haiku 4.5 $0.00002 $0.00166

Measured 4d ago against content hash df3e0e450569, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

service-check 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 4d 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.

plugins/mycelium/skills/service-check/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Service Check Skill

Evaluate against Lou Downe's 15 principles.

Checklist

For each principle, assess: Pass / Partial / Fail / N/A

  1. Easy to find: Can users find this service without knowing its name?

    • Discoverable through natural search terms
    • Linked from logical starting points
  2. Clearly explains its purpose: Is it immediately clear what this does?

    • Purpose statement visible without scrolling
    • Target audience identifiable
  3. Sets expectations: Do users know what will happen?

    • Timeline/process visible upfront
    • Requirements stated before starting
  4. Enables completion: Can users finish what they came to do?

    • End-to-end journey works
    • No organizational barriers blocking completion
  5. Familiar: Does it work the way users expect?

    • Uses conventions users know
    • No surprising behavior
  6. No prior knowledge needed: Can a new user succeed?

    • No jargon or acronyms without explanation
    • No assumed context
  7. Agnostic of org structures: Are internal boundaries invisible?

    • Users don't need to know which department handles what
    • No internal handoffs visible to users
  8. Minimum steps: Is every step necessary?

    • No redundant data entry
    • No unnecessary confirmation steps
  9. Consistent: Is language/design uniform throughout?

    • Same terms used for same concepts
    • Visual patterns consistent
  10. No dead ends: Is there always a next step?

    • Error states have recovery paths
    • Edge cases have guidance
  11. Usable by everyone: Is it accessible and inclusive?

    • WCAG 2.1 AA compliant
    • Works across devices and assistive technologies
  12. Encourages right behaviors: Does design nudge good outcomes?

    • No dark patterns (confirmshaming, hidden costs, forced continuity, misdirection, roach motel, trick questions, bait-and-switch)
    • Default options are the safe/good ones
    • Behavioral science used to HELP users, not exploit them (Shotton: ethical application)
    • If dark patterns detected: flag "Dark Pattern Marketing" anti-pattern (see ${CLAUDE_PLUGIN_ROOT}/harness/anti-patterns.md)

Read the full file on GitHub · 148 lines

Changes

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.

  1. 4d ago Changed · +41 lines df3e0e450569
  2. 8d ago First seen · 107 lines · 21 tokens per session scan A 666045f6d4fe

Subscribe to this mod's changes

service-check is a skill published in the GitHub repository haabe/mycelium (45 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,657 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

skill-finder

Find the right Affitor skill for your goal. Triggers on: "which skill should I use", "find me a skill", "what skills are available", "help me choose a skill", "skill for SEO", "skill for email", "explore skills", "I'm new to Affitor", "what can Affitor do", "search skills", "skill for blog writing", "skill for landing…

Affitor/affiliate-skills · 94 tokens

meraki-network-ops

Cisco Meraki organization and network operations (read-only) — org discovery, network inventory, device inventory, clients, group policies, admins, licensing, alert settings via Cisco's official Meraki MCP. Use as the entry point for any Meraki question, to discover org and network IDs, or to inventory Meraki networks…

automateyournetwork/netclaw · 72 tokens

auto

Intent-classified router, the front door to OrchestKit and the DEFAULT entry point for any goal-shaped request. Classifies a plain-English goal and routes it to the right specialist skill. Routing is never overhead, so use it even when the target skill seems obvious; skip only when already executing inside another…

yonatangross/orchestkit · 99 tokens

gingiris-user-interview

A playbook for interviewing users and operating an early product launch, including screening participants, running interviews, testing beta versions, and reviewing churn. It is based on a described process for finding product-market fit, meaning a product consistently meeting a real user need.

Gingiris-1031/gingiris-skills · 369 tokens

tao-setup

One-time session setup and orchestration map for the TAO skill bank. Run this first when the TAO skills were installed individually (e.g. from a public skills catalog) so the session gets the cross-skill discovery flow, credential checks, and host preflight that the bundled plugin hook would otherwise inject…

NVIDIA-TAO/tao-skill-bank · 97 tokens

tao-list-capabilities

Answer what the TAO Skill Bank plugin can do by generating the response from packaged application, data, model, AutoML, and platform manifests. Use when the user asks "what can TAO Skill Bank do", "list TAO models", "which TAO workflows are available", or "what supports AutoML".

NVIDIA-TAO/tao-skill-bank · 70 tokens