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.
/plugin marketplace add christopherkarani/ryk/plugin install rykWrote 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/christopherkarani/ryk/doctor)<a href="https://agentmods.dev/skills/christopherkarani/ryk/doctor"><img src="https://agentmods.dev/badge/skills/christopherkarani/ryk/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.1 | $0.00000 | $0.00400 |
| Opus 5 | $0.00000 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
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 6d 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.
What it actually says
doctor
Check ryk installation, policy status, host integration status, and plugin readiness.
When to use
Use this skill when you want to verify that ryk is properly installed, that a policy exists for the current repository, and that the Claude Code plugin integration is ready.
Commands
Run the ryk plugin doctor for Claude Code:
ryk plugin doctor claude
Run the general ryk doctor for platform capabilities:
ryk doctor
Interpreting results
Missing ryk binary
If ryk is not found in PATH, install ryk first. Build from source with Zig 0.16.0:
./scripts/zig build
The binary will be at ./zig-out/bin/ryk.
Missing policy
If .ryk/policy.yaml is missing, initialize one:
ryk init --preset claude-code
If the claude-code preset is not available, use the closest plugin-safe preset:
ryk init --preset generic-agent
Then validate it:
ryk policy check .ryk/policy.yaml
Missing Claude Code plugin install
If the plugin directory is not detected, ensure the ryk repository includes integrations/claude-code-plugin/ and that you are running from the workspace root.
Follow-up diagnostics
If the doctor reports warnings:
- Read the warning message carefully.
- Fix missing policies or binaries.
- Re-run
ryk plugin doctor claudeto confirm. - If issues persist, run
ryk doctorfor platform-specific capability notes.
Notes
- This skill does not modify host configuration.
- The plugin does not collect telemetry. Release CLI commands may record only fixed anonymous metadata; see
docs/telemetry.md. - The doctor output goes to stdout; errors go to stderr.
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.
- 6d ago First seen · 73 lines · 0 tokens per session scan A 4f5df3298025
doctor is a skill published in the GitHub repository christopherkarani/ryk (39 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 400 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-30.
Other skills, from other repositories
ffuf-claude-skill
Skill "ffuf-claude-skill" from Agent-Threat-Rule/agent-threat-rules, covering ffuf claude skill, when to use this skill and instructions.
comfy-debug-preview
ComfyUI debug/preview nodes: show text/numbers/JSON/tensor shapes, image previews, counts, VRAM/CPU telemetry, timing. Use when inspecting a value mid-graph without changing it.
code-hidden-failures
Scan for hidden failures: swallowed errors (empty catch, || true, 2>/dev/null) and silent degradation (success on zero results). Use when failures vanish or success masks empty output.
comfy-metadata
Extract/analyze ComfyUI metadata embedded in output files - PNG tEXt, WebP EXIF, MP4/WebM container, .latent safetensors. Use when figuring out what prompt/settings produced a file, or comparing runs.
configure-sentry
Sentry error tracking setup. Use when installing the Sentry SDK, fixing hardcoded DSNs, or adding source map upload for frontend, Next.js, Node, or Python.
configure-dead-code
Dead-code detection: Knip, Vulture, cargo-machete, deadcode. Use when setting up unused-code scanning, migrating tools, or adding dead-code CI checks.