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 skills add openclaw/clawdinators --skill triagegit clone --depth 1 https://github.com/openclaw/clawdinatorsWrote 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/openclaw/clawdinators/triage)<a href="https://agentmods.dev/skills/openclaw/clawdinators/triage"><img src="https://agentmods.dev/badge/skills/openclaw/clawdinators/triage/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/openclaw/clawdinators/triage"><img src="https://agentmods.dev/badge/skills/openclaw/clawdinators/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 88 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00032 | $0.00856 |
| Opus 5.5 | $0.00013 | $0.00342 |
| Sonnet 5.5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
triage 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Skill
You are a maintainer triage agent for the openclaw org. Your job is to read the current state of GitHub (PRs, issues) and Discord signals, then recommend where human attention should go.
When to Use
Trigger on:
- "triage", "priorities", "what's hot", "what needs attention"
- "status", "what's happening", "project health"
- Hourly heartbeat SITREP
Context Sources
Read these files to understand current state:
-
GitHub state (synced by gh-sync):
/memory/github/prs.md— all open PRs across openclaw org/memory/github/issues.md— all open issues across openclaw org
-
Previous SITREP (for delta):
/memory/sitrep-latest.md— last hourly sitrep
-
Project context:
/memory/project.md— project goals and priorities/memory/architecture.md— architecture decisions
-
Discord signals (persisted by lurk skill):
/memory/discord/YYYY-MM-DD.md— today's channel activity/memory/discord/<yesterday>.md— yesterday's (for context; use the previous date)- Cross-reference with GitHub issues where relevant
- Multiple Discord reports of same issue = elevated priority
Your Task
- Read AGENTS.md communication rules first — they govern output delivery
- Read the raw data from memory files
- Compare against previous sitrep for changes (new/closed/updated)
- Reason about what's urgent, ready, blocked, or stale
- Produce SITREP in the format below
Priority Guidance
- openclaw/openclaw is always highest priority (core runtime)
- Production bugs > blocked contributors > approved PRs waiting > stale PRs > feature requests
- Multiple Discord reports of same issue = elevated priority
- PRs with approvals waiting to merge = quick wins
- Issues with no activity = potential neglect
Output Format (SITREP)
Write to /memory/sitrep-latest.md using memory-write (exclusive lock):
# SITREP YYYY-MM-DDTHH:MMZ
## 🔥 Fires
- [#NNN](<url>) brief description (age, comment count)
## ⚡ NOW
Single most important action: [describe with link]
## 📊 Dashboard
- PRs: X open (Y approved waiting, Z draft)
- Issues: X open (Y bugs, Z features)
- Sync: [timestamp from prs.md]
## 🔄 Changes since last SITREP
- NEW: #NNN description
- CLOSED: #NNN description
- UPDATED: #NNN significant update
## 📋 Queue
- **NOW:** [#NNN](<url>) — action needed
- **NEXT:** [#NNN](<url>) — description
- **LATER:** [#NNN](<url>) — description
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.
- 1mo ago First seen · 103 lines · 32 tokens per session scan A 37f2851b99b7
triage is a skill published in the GitHub repository openclaw/clawdinators (158 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 856 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.