Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/christopherkarani/ryknpx agentmods add skills/christopherkarani/ryk/ryk-doctorWrote 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/ryk-doctor)<a href="https://agentmods.dev/skills/christopherkarani/ryk/ryk-doctor"><img src="https://agentmods.dev/badge/skills/christopherkarani/ryk/ryk-doctor/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/christopherkarani/ryk/ryk-doctor"><img src="https://agentmods.dev/badge/skills/christopherkarani/ryk/ryk-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
ryk-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 9d 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
ryk-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 Codex plugin integration is ready.
Commands
Run the ryk plugin doctor for Codex:
ryk plugin doctor codex
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 codex
Then validate it:
ryk policy check .ryk/policy.yaml
Missing Codex plugin install
If the plugin directory is not detected, ensure the ryk repository includes integrations/codex-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 codexto 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.
- 9d ago First seen · 67 lines · 0 tokens per session scan A f8c9fa0f9244
ryk-doctor is a skill published in the GitHub repository christopherkarani/ryk (39 stars, last pushed 19d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 370 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
debug-triage
Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
systematic-debug
A structured debugging workflow that moves from observing an error to reproducing it, testing possible causes, fixing it, and preventing regression.
hypothesis-debug
A structured method for debugging failures by comparing multiple possible causes and testing which ones the evidence rules out. It examines code, the environment, data, and measurement errors.
build-fix
A step-by-step process for fixing build and type-checking errors in projects such as TypeScript, Java, Python, or Rust.
systematic-debugging
Systematic debugging approach for errors, test failures, and unexpected behavior. Use when encountering bugs, test failures, errors, or when debugging is needed. Prevents common anti-patterns like random fixes, skipping root cause analysis, and thrashing.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.