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 agentmods add skills/sandsower/beislid/doctornpx skills add sandsower/beislid --skill doctorgit clone --depth 1 https://github.com/sandsower/beislidWrote 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/sandsower/beislid/doctor)<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>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 | $0.00080 | $0.07919 |
| Opus 5 | $0.00040 | $0.03960 |
| Sonnet 5 | $0.00016 | $0.01584 |
| Haiku 4.5 | $0.00008 | $0.00792 |
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.
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. Rungit inithere, 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:
-
$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.mdfound in.beislid/. If this is a fresh project, run/setupto create one. If you moved your config, restore it to<repo>/.beislid/workflow.md. -
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.
-
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 -->
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.
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.
- 5d ago First seen · 304 lines · 80 tokens per session scan A d7c9b6342823
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…