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 meta-skillgit 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/meta-skill)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/meta-skill"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/meta-skill/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/meta-skill"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/meta-skill.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.00128 | $0.01149 |
| Opus 5 | $0.00064 | $0.00575 |
| Sonnet 5 | $0.00026 | $0.00230 |
| Haiku 4.5 | $0.00013 | $0.00115 |
Grade A, and why
meta-skill 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 11d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
meta-skill
The thesis: AI agents writing arbitrary code is risky and unbounded. AI agents filling a structured template under hard validation is bounded and shippable. This skill is the demonstration: a tightly-shaped pipeline where the LLM authors only the parts of a new skill that humans would hand-write anyway, while the bash skeleton, error handling, and gate calls are generated deterministically.
Procedure
bash skills/meta-skill/run.sh "I need a skill that watches X for Y and writes to Z"
bash skills/meta-skill/run.sh --dry-run "<problem>" # parse + validate, no write
Pipeline
- Parse the problem string via local Ollama qwen3.5:latest. Extract:
skill_name(kebab-case, 3-6 words)owner_agent(one of: content, builder, ops, sales, research, accountant, trading, hermes)description(one sentence, voice-rule-compliant)pipeline_steps(3-7 numbered steps)trigger(cron / event / manual / on-skill-call)inputs(named parameters; empty list OK)outputs(paths or stdout shape)
- Generate
SOUL.md(intent + failure mode + voice anchor; 100-200 words). - Generate
SKILL.md(frontmatter + procedure + status codes; static template filled with extracted fields). - Generate
run.sh(skeleton with proper error handling, voice-gate calls if outputs are text-bound, smoke-test stub, TODO markers for the actual pipeline body). - Validate:
a.
python3 tools/voice/score.pyon the SKILL.md description → must score >= 60. b.python3 tools/voice/scrubber.pyon the description → must pass. c.bash -n run.sh→ must pass syntax check. d. Smoke-test:bash run.sh --dry-run→ must exit non-error (rc != 2) and produce aSTATUS=line. - Land:
- If all 4 validations pass → write to
~/.openclaw/skills/<name>/(or~/.hermes/skills/<name>/for hermes-owned). - If any fails → write to
data/proposed_skills/cont-17-meta/<name>/for Cooper review, with a_VALIDATION.mdfile detailing what failed.
- If all 4 validations pass → write to
- Output JSON to stdout:
{status, skill_path, smoke_test_result, gates_passed}.
What ships with it
2 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.
- 11d ago First seen · 89 lines · 128 tokens per session scan A 648bd8239cea
meta-skill is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 128 tokens to every session and 1,149 once invoked, about $0.0006 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-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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…