Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .claude/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add ohdearapp/ohdear-cli --skill ohdear -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .agents/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ohdearapp/ohdear-cli --skill ohdear -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .cursor/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add ohdearapp/ohdear-cli --skill ohdear -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .gemini/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install ohdearapp/ohdear-cli ohdear
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add ohdearapp/ohdear-cli --skill ohdear -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .github/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ohdearapp/ohdear-cli --skill ohdear -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "ohdear" agent skill from https://github.com/ohdearapp/ohdear-cli/tree/main/skills/ohdear into .opencode/skills/ohdear/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ohdear", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
ohdear
GitHub stars
141
Token cost
~1.1k tokens
SKILL.md length
375 words
Files
3 (incl. references)
Skills in repo
1
Repo updated
First seen
Licence
MIT
At a glance
Manage Oh Dear website monitoring using the ohdear CLI. An agent skill from ohdearapp/ohdear-cli.
S message contains an ohdear.app URL (e.g
SKILL.md covers Prerequisites, Authentication, Command naming and Output, plus 3 more sections
Calls jq and composer; reaches ohdear.app
The user wants to check if their site is up
What it does
Ohdear is an agent skill from ohdearapp/ohdear-cli. Manage Oh Dear website monitoring using the ohdear CLI. ALWAYS activate when the user's message contains an ohdear.app URL (e.g. https://ohdear.app/monitors/123/check/broken-links/report). Extract the monitor ID and check type from the URL and use the CLI to fetch the data. Also use when the user wants to check if their site is up, view uptime or downtime, list or manage monitors, view broken links, mixed content, or certificate health, manage maintenance periods or status pages, configure cron checks, view DNS…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/commands.md` and `references/workflows.md`).
It sits in Productivity & Automation, covering Web performance, Network security and Scheduled and recurring tasks. The repository describes itself as: The official Oh Dear CLI. The licence is MIT.
When your agent uses it
S message contains an ohdear.app URL (e.g
The user wants to check if their site is up
Manage monitors
View broken links
Example prompts
“/ohdear”
What it can do on your machine
Read from SKILL.md and the folder at commit ed9926e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
composer
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
ohdear.app
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Ohdear loads about 1.1k tokens when it runs, and up to ~5k if it reads all its reference files. Until then it costs about 200 tokens; SKILL.md has 375 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~200
When it runs· the whole SKILL.md, loaded when a task matches
~1.1k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~5k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/ohdear/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
ohdear
description
Manage Oh Dear website monitoring using the ohdear CLI. ALWAYS activate when the user's message contains an ohdear.app URL (e.g. https://ohdear.app/monitors/123/check/broken-links/report). Extract the monitor ID and check type from the URL and use the CLI to fetch the data. Also use when the user wants to check if their site is up, view uptime or downtime, list or manage monitors, view broken links, mixed content, or certificate health, manage maintenance periods or status pages, configure cron checks, view DNS history or DNS blocklists, check port scan results, view sitemap checks, check application health, view Lighthouse performance reports, view crawled URLs summary and details, manage tags, manage notification destinations, manage teams, or interact with ohdear.app in any way.
license
MIT
metadata.author
ohdearapp
metadata.version
5.2.0
Oh Dear CLI
The ohdear CLI manages Oh Dear website monitoring from the terminal. Every Oh Dear API endpoint has a corresponding command.
Prerequisites
bash
ohdear --version # Check if installed
composer global require ohdearapp/ohdear-cli # Install if needed
Authentication
bash
ohdear login # Prompted for API token (get it at https://ohdear.app/user-settings/api)
ohdear logout # Clear credentials
If any command returns 401, run ohdear login again.
Command naming
Commands use kebab-case names exactly as listed in references/commands.md. Do NOT guess command names — always look them up. Common mistakes to avoid:
sites:list → list-monitors
monitors:get → get-monitor
uptime:get → get-uptime
Always check references/commands.md before running a command. If unsure, run ohdear <command> --help to verify parameters.
Output
Commands output human-readable text by default. For any task that requires analysis, comparison, filtering, or counting, always use --json to get structured output you can parse:
bash
ohdear list-monitors --json # Get all monitors as JSON
ohdear get-uptime --monitor-id=1 --json # Get uptime data as JSON
Other format options: --yaml, --minify. Use -H to include response headers.
Note:--json works on API commands (list-, get-, etc.), not on utility commands (login, logout, clear-cache).
JSON structure:--json responses are paginated objects{data: [...], links: ...}, not bare arrays. Always use .data[] to access items (e.g. jq '.data[]'), never .[].
Teams
API keys are user-scoped. A user may belong to multiple teams. Monitors have a team_id field but no team_name. To resolve team names to IDs:
bash
ohdear get-me --json | jq '.teams[] | {id, name}'
Then filter monitors by team_id. Do NOT use list-managed-teams — that's a reseller-only endpoint.
When presenting results to the user, summarize clearly:
Monitors: Table with ID, URL, friendly name, status, checks enabled
Uptime: Percentage uptime and downtime periods with start/end times
Broken links: URLs with HTTP status codes and source page (use --run-id with historical run IDs to compare across runs — see workflows)
Crawled URLs: Always start with get-crawled-urls-summary (tiny payload: totals + by-type breakdown). Only use list-crawled-urls-details with jq filters — it returns 100 items/page and can be very large. Never dump raw details into context.
Certificate health: Issuer, expiration date, and issues found
Cron checks: Name, frequency, last ping time, status
Status pages: Title, URL, associated monitors
Lighthouse reports: Performance, accessibility, best practices, SEO scores
Show full SKILL.md (69 more words)Show less
Documentation
Oh Dear docs are available in clean markdown for easy reading. Append .md to any docs URL or request with Accept: text/markdown:
Ohdear next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
Systematically map and remove malware, backdoors, and attacker persistence mechanisms (registry Run keys, scheduled tasks, WMI subscriptions, services, cron/init.d) from infected Windows and Linux…
Manage Oh Dear website monitoring using the ohdear CLI. An agent skill from ohdearapp/ohdear-cli. Ohdear is an agent skill from ohdearapp/ohdear-cli. Manage Oh Dear website monitoring using the ohdear CLI.
When should I use Ohdear?
Ohdear fits situations like: S message contains an ohdear.app URL (e.g; the user wants to check if their site is up; manage monitors; view broken links.
How do I install Ohdear in Claude Code?
Run `npx skills add ohdearapp/ohdear-cli --skill ohdear -a claude-code`. Or copy the skill folder (skills/ohdear in ohdearapp/ohdear-cli) into .claude/skills/ohdear in your project. Claude Code loads it when a task matches its description.
How do I install Ohdear in Codex?
Run `npx skills add ohdearapp/ohdear-cli --skill ohdear -a codex`. Or copy the skill folder (skills/ohdear in ohdearapp/ohdear-cli) into .agents/skills/ohdear in your project. Codex loads it when a task matches its description.
Can I use Ohdear in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ohdearapp/ohdear-cli --skill ohdear -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ohdear, .gemini/skills/ohdear, .github/skills/ohdear and .opencode/skills/ohdear in your project.
What does Ohdear need to run?
Going by SKILL.md and its folder, Ohdear needs the command-line tools its instructions call (jq and composer).
Does Ohdear access the network?
SKILL.md names 1 domain. In commands or code: ohdear.app; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Ohdear safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Ohdear use?
Ohdear is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Ohdear use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Ohdear?
Skills that share tags, products or a category with Ohdear: Implementing File Integrity Monitoring With Aide (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Alibabacloud Ecs Windows Os Troubleshooting (aliyun/alibabacloud-ecs-troubleshoot-skills, 148 stars), Convex Launch Readiness (openclaw/clawhub, 9.5k stars) and Hunting For Scheduled Task Persistence (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Ohdear?
ohdearapp (a GitHub organization) maintains it in ohdearapp/ohdear-cli, which has 141 GitHub stars. The repository was last updated on September 7, 2026.
Source: ohdearapp/ohdear-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.