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 dailyaiagents-cpu/dailyai-os --skill skill-registry-syncgit clone --depth 1 https://github.com/dailyaiagents-cpu/dailyai-osWrote 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/dailyaiagents-cpu/dailyai-os/skill-registry-sync)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/skill-registry-sync"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-registry-sync/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/dailyaiagents-cpu/dailyai-os/skill-registry-sync"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-registry-sync.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00062 | $0.02090 |
| Opus 5 | $0.00031 | $0.01045 |
| Sonnet 5 | $0.00012 | $0.00418 |
| Haiku 4.5 | $0.00006 | $0.00209 |
Grade A, and why
skill-registry-sync scanned grade A with 1 finding 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 10d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
subprocess.run( How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-registry-sync
Why this exists
Every new skill needs to be listed in its owner-agent's SOUL.md "Available Skills" section, otherwise the agent doesn't know to dispatch to it. This has been forgotten in 3 recent ship sessions, causing silent dispatch failures Cooper had to debug manually. This skill makes the wire-in automatic.
Inputs
{
"dry_run": false
}
dry_run=true walks the skills, computes the would-be block, prints the diffs, but does NOT modify any SOUL.md.
Procedure
Step 1 — Walk skills + parse frontmatter
import pathlib, re, json, subprocess, datetime
home = pathlib.Path.home()
skills_dir = home / ".openclaw/skills"
# Map agent_id → list of skill names
by_agent = {}
no_owner = []
for skill_dir in sorted(skills_dir.iterdir()):
if not skill_dir.is_dir():
continue
soul_path = skill_dir / "SOUL.md"
if not soul_path.exists():
continue
text = soul_path.read_text(errors="replace")
# Parse leading --- frontmatter
m = re.match(r"^---\n(.*?)\n---\n", text, re.DOTALL)
if not m:
no_owner.append(skill_dir.name)
continue
fm = m.group(1)
owner_match = re.search(r"^owner_agent:\s*(.+?)\s*$", fm, re.MULTILINE)
if not owner_match:
no_owner.append(skill_dir.name)
continue
owner = owner_match.group(1).strip()
by_agent.setdefault(owner, []).append(skill_dir.name)
# Sort skills alphabetically per agent
for k in by_agent:
by_agent[k].sort()
print(f"[registry] {sum(len(v) for v in by_agent.values())} skills with owner_agent across {len(by_agent)} agents")
print(f"[registry] {len(no_owner)} skills without owner_agent (skipped, see WARN log)")
Step 2 — Locate SOUL.md files (repo + runtime)
repo = home / "Dev/daily-ai-agent-os"
def soul_pair(agent_id):
if agent_id == "main":
return [
repo / "tools/hermes/SOUL.md",
home / ".hermes/SOUL.md",
]
repo_soul_candidates = [
repo / f"openclaw/{agent_id}-agent/SOUL.md",
repo / f"openclaw/{agent_id}-commander-agent/SOUL.md", # ops uses ops-commander-agent
]
repo_soul = next((p for p in repo_soul_candidates if p.exists()), repo_soul_candidates[0])
return [
repo_soul,
home / f".openclaw/agents/{agent_id}/SOUL.md",
]
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 231 lines · 62 tokens per session scan A feb935f21e63
skill-registry-sync is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,090 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…