doctor

doctor is a skill for Claude Code, Codex from sandsower/beislid. It costs 80 tokens per session (7,919 once invoked), scanned A, original, MIT.

A read-only workflow audit skill that checks a project's Beislið configuration and tests each configured capability. Beislið is the workflow system this skill belongs to.

In plain words
What is it for?
It is for checking workflow setup, probing configured tools, refreshing capability checks, and reporting gaps in plain language.
Why use it?
It shows which workflow settings and capabilities are available or missing without changing the project's configuration or skills.

Skill for Claude CodeCodex

Part of the beislid plugin — 22 skills shipped together

Install

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.

agentmods
npx agentmods add skills/sandsower/beislid/doctor
Any agent
npx skills add sandsower/beislid --skill doctor
Clone the repo
git clone --depth 1 https://github.com/sandsower/beislid

Made for: Claude Code, Codex.

Or install beislid, the plugin that ships this one along with the rest of its 22 skills.

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 doctor

README.md
[![agentmods](https://agentmods.dev/badge/skills/sandsower/beislid/doctor.svg)](https://agentmods.dev/skills/sandsower/beislid/doctor)
Your own site
<a href="https://agentmods.dev/skills/sandsower/beislid/doctor"><img src="https://agentmods.dev/badge/skills/sandsower/beislid/doctor.svg" alt="Measured on agentmods" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,919 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00080 $0.07919
Opus 5 $0.00040 $0.03960
Sonnet 5 $0.00016 $0.01584
Haiku 4.5 $0.00008 $0.00792

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

Security

Grade A, and why

doctor 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 5d 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.

skills/doctor/SKILL.md · 304 lines

How it starts

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

Doctor

Audit a project's Beislið workflow config end-to-end. Read <repo>/.beislid/workflow.md, probe each configured capability against the current host session, write a probe cache that orchestrators consume, and print a conversational audit.

Doctor is read-only on the repo and write-only on the cache. It does not modify workflow.md, install or remove skills, post comments, or invoke other orchestrators.

Pass --refresh to force a full re-probe even when the cache is fresh.


1. Precheck — git repo required

Run via Bash:

git rev-parse --show-toplevel

If exit code ≠ 0, hard-fail with this prose and stop:

🛑 Doctor needs a git repository. Beislið workflow config lives at <repo>/.beislid/workflow.md. Run git init here, make at least one commit, then re-run /doctor.

Capture the repo root path for later steps ($git_root).

Also verify there is at least one commit:

git rev-list --max-parents=0 HEAD | head -1

If exit ≠ 0 or output is empty, hard-fail with the same prose pattern adjusted to "make at least one commit." No path-hash fallback.

2. Read inputs

Read three files in this order:

  1. $git_root/.beislid/workflow.md — the config under audit. If the Read fails (file does not exist), hard-fail with the two-clause prose and stop:

    🛑 No workflow.md found in .beislid/. If this is a fresh project, run /setup to create one. If you moved your config, restore it to <repo>/.beislid/workflow.md.

  2. probe-semantics.md (relative to this SKILL.md, resolved through the per-skill symlink). If the Read fails (broken symlink), hard-fail:

    🛑 Doctor's probe-semantics aux is unreadable — likely a broken symlink. Re-run the Beislið installer to repair it.

  3. workflow-md-format.md (relative to this SKILL.md, same pattern). Same broken-symlink message tailored to the format spec.

3. Validate the version stamp

The first line of workflow.md MUST match exactly:

<!-- beislid-workflow: v1 -->

Read the full file on GitHub · 304 lines

Files

What ships with it

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

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. 5d ago First seen · 304 lines · 80 tokens per session scan A d7c9b6342823

Subscribe to this mod's changes

doctor is a skill published in the GitHub repository sandsower/beislid (10 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 7,919 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens