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/mudrii/openclaw-dashboard/project-opsnpx skills add mudrii/openclaw-dashboard --skill project-opsgit clone --depth 1 https://github.com/mudrii/openclaw-dashboardWrote 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/mudrii/openclaw-dashboard/project-ops)<a href="https://agentmods.dev/skills/mudrii/openclaw-dashboard/project-ops"><img src="https://agentmods.dev/badge/skills/mudrii/openclaw-dashboard/project-ops.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.00038 | $0.00316 |
| Opus 5 | $0.00019 | $0.00158 |
| Sonnet 5 | $0.00008 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
project-ops 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.
What it actually says
Project Ops
This is the native Codex operations skill for this repository.
Use it when:
- changing build, test, lint, or check workflows
- editing
Makefileor CI workflows - reviewing release and packaging behavior
- validating commands agents should run in this repo
Source Of Truth
go.moddefines the Go toolchain level.Makefiledefines the preferred local command surface..github/workflows/defines CI expectations.- If these disagree with prose docs, follow code and workflow config first.
Repository Expectations
- Prefer
make build,make test,make lint,make check. - Keep local and CI command surfaces aligned.
- Do not invent commands that the repo does not expose.
- Preserve the zero-dependency bias unless a change explicitly requires otherwise.
- Treat release workflow changes as operational changes that need careful compatibility review.
Change Discipline
- Keep command names stable when possible.
- If command behavior changes, update docs in the same change.
- Prefer small operational changes with obvious rollback paths.
- Do not weaken checks casually to make a change pass.
Review Focus
- command drift between docs, Makefile, and CI
- hidden dependency additions
- missing vet/lint/test coverage in local or CI paths
- release workflow mismatches
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 · 44 lines · 38 tokens per session scan A 71035adb119f
project-ops is a skill published in the GitHub repository mudrii/openclaw-dashboard (454 stars, last pushed 4d ago), licensed MIT. It adds 38 tokens to every session and 316 once invoked, about $0.0002 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-30.
Other skills, from other repositories
sentry-triage
Triage WorldMonitor Sentry issues — classify unresolved events as noise, already-fixed, product bugs, or needs-human; optionally ship a tested fix. Use when the user says triage Sentry, pastes a WORLDMONITOR- ID or sentry.io URL, or asks to investigate production errors.
verify-worldmonitor
Launch and drive the WorldMonitor browser dashboard (Vite app at /dashboard) to prove user-facing behavior with screenshots and transcripts. Use when a change needs proof in the real app rather than only unit tests — panels, map layers, settings, search, country briefs, boot — or when asked to run, screenshot, or…
fetch-news-digest
Retrieve the pre-aggregated digest of World Monitor's curated news feeds, bucketed by category, with per-article threat classification and alert flags. Use when the user asks what's in the news right now, wants headlines by topic, or needs a current-events sweep.
assess-energy-shock
Model oil or gas supply shock exposure for a country and chokepoint. Use when the user asks how an energy disruption could affect fuel supply, strategic cover, or product deficits.
check-chokepoint-status
Retrieve live disruption status for the 13 monitored maritime chokepoints (Suez, Hormuz, Malacca, Bab el-Mandeb, Panama, and more). Use when the user asks whether a strait or canal is disrupted, congested, or safe for shipping right now.
check-forecast-signals
Retrieve probabilistic forecasts and their scorecard context. Use when the user asks what World Monitor is forecasting, how probabilities shifted, or how calibrated the forecasts are.