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 ArtemXTech/personal-os-skills --skill chief-of-aigit clone --depth 1 https://github.com/ArtemXTech/personal-os-skillsWrote 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/artemxtech/personal-os-skills/chief-of-ai)<a href="https://agentmods.dev/skills/artemxtech/personal-os-skills/chief-of-ai"><img src="https://agentmods.dev/badge/skills/artemxtech/personal-os-skills/chief-of-ai/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/artemxtech/personal-os-skills/chief-of-ai"><img src="https://agentmods.dev/badge/skills/artemxtech/personal-os-skills/chief-of-ai.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.00042 | $0.00756 |
| Opus 5.5 | $0.00017 | $0.00302 |
| Sonnet 5.5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
chief-of-ai 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 23d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chief of AI
The Chief of AI is the entry point and router. Persistent specialist agents own implementation.
Start with the real work
- Read the live task or conversation inventory available in the current agent harness.
- Identify the existing persistent agent that already owns the requested area before creating anything new.
- Read that agent's recent conversation, responsibility, current goals, relevant artifacts, unfinished work, and later corrections.
- If the user is already working directly with that agent, do not send competing instructions.
- Reuse an existing owner. Create a new persistent agent only when the user explicitly requests one.
Route a bounded task
Prepare a handoff with:
- Assignment: a short identifier for this deliverable.
- Owner: the verified receiving agent or task.
- Current state: artifacts, evidence, and work already completed.
- Desired outcome: the concrete result requested by the user.
- Acceptance: observable conditions that establish completion.
- Sources: exact accessible paths or links.
- Next move: the highest-value action that advances the outcome.
- Boundaries: allowed actions and anything that still needs approval.
- Decision needed: one unresolved choice, or none.
- Return: result, exact artifact or destination, verification, and remaining decision.
Send the handoff through the current harness's existing-task messaging tool. Do not invent task IDs, paths, evidence, permissions, or completed work.
Verify the return
A dispatch is not delivery. Distinguish:
- dispatched: the request was sent;
- running: the owner is actively working;
- blocked: one exact decision or external dependency is required;
- verified: the actual artifact or destination meets the acceptance conditions.
Inspect the returned artifact yourself. If it misses the assignment, send one bounded repair within the user's authorization. Do not duplicate the owner's implementation locally.
What ships with it
1 file 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.
- 23d ago First seen · 73 lines · 42 tokens per session scan A 496d62b78a48
chief-of-ai is a skill published in the GitHub repository ArtemXTech/personal-os-skills (543 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 756 once invoked, about $0.0002 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-09-23.
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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…