Home / canonry / canonry · packages/api-routes/src/doctor/AGENTS.md · GitHub

AGENTS.md@packages/api-routes/src/doctor agentsA

Name: AGENTS.md@packages/api-routes/src/doctor
Author: canonry

AGENTS.md@packages/api-routes/src/doctor is agent-read markdown (agents) from canonry/canonry.

Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.

What the file says

# doctor

`canonry doctor` runs an extensible set of health checks across global config and project-scoped integrations. Each check has a stable dotted ID (`google.auth.connection`, `ga.auth.connection`, `config.providers`, …) so an agent or skill can filter via `--check <id>` / `?check=<id>` and react to specific failures programmatically.

- **CLI:** `canonry doctor [--project <name>] [--check <id>...] [--format json]`
- **API:** `GET /api/v1/doctor` (global), `GET /api/v1/projects/:name/doctor` (project-scoped). Both accept `?check=<comma-separated ids or wildcards>`.
- **MCP:** `canonry_doctor` (core tier) — passes `project` + `checks[]` straight through.

Each check returns `status: ok | warn | fail | skipped`, a stable machine-readable `code`, a `summary`, optional `remediation`, and structured `details`. v1 ships:

| Category | ID | Scope | Purpose |
|----------|----|-------|---------|
| database | `db.file.present` | global | Configured SQLite database file still exists on disk (catches `rm ~/.canonry/data.db` against a running daemon — SQLite holds the inode open across `unlink`) |
…

Read the whole file at its exact version.

How to install

Latest version

mdr add canonry/canonry/packages/api-routes/src/doctor/AGENTS.md@git:20260921.1697bee

Exact content

mdr add canonry/canonry/packages/api-routes/src/doctor/AGENTS.md@sha256:4d3e5bb08962713d

Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.

Badge

[![mdr](https://markdownregistry.com/badge/art_hcuxt63tkglcirqi.svg)](https://markdownregistry.com/a/art_hcuxt63tkglcirqi)

1 badge views in 30 days

Versions

version	committed	commit	size	audit
git:20260921.1697bee latest	2026-09-21	1697bee	11,473 B	A	view · diff
git:20260919.46b60a6	2026-09-19	46b60a6	11,243 B	A	view

Audit of the latest version

A 14 of 14 checks passed. Deterministic, no model, same answer every run.

pass: Size between 200 bytes and 200 KB (11473 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

canonry/canonry · 153 stars · license MIT · pushed 2026-09-24 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_hcuxt63tkglcirqi
GET https://markdownregistry.com/api/v1/resolve?ref=canonry/canonry/packages/api-routes/src/doctor/AGENTS.md
GET https://markdownregistry.com/api/v1/blob/4d3e5bb08962713d59a7eb39d82d0d254d37538b53860b87c4734241624a81cd

Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.