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 JOINCLASS/ai-ceo-framework --skill upgrade-automationgit clone --depth 1 https://github.com/JOINCLASS/ai-ceo-frameworkWrote 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/joinclass/ai-ceo-framework/upgrade-automation)<a href="https://agentmods.dev/skills/joinclass/ai-ceo-framework/upgrade-automation"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/upgrade-automation/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/joinclass/ai-ceo-framework/upgrade-automation"><img src="https://agentmods.dev/badge/skills/joinclass/ai-ceo-framework/upgrade-automation.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.00021 | $0.00565 |
| Opus 5.5 | $0.00008 | $0.00226 |
| Sonnet 5 | $0.00004 | $0.00113 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
upgrade-automation 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 today.
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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/upgrade-automation -- Automation Upgrade Skill
Periodically check for new Claude Code and Anthropic features, identify those applicable to your automation, and propose/implement upgrades.
Information Sources
- Anthropic Blog: https://www.anthropic.com/news
- Claude Code Documentation: https://docs.anthropic.com/en/docs/claude-code
- Claude Code Release Notes: Check
claude --version - GitHub: https://github.com/anthropics
- Community articles: Claude Code tags on dev platforms
- Social media: @AnthropicAI official posts
Evaluation Criteria
Rate each new feature on 5 dimensions (10 points each, 50 total):
| Dimension | What to Evaluate |
|---|---|
| Automation impact | How much manual work does this eliminate? |
| Adoption cost | Implementation time and complexity |
| Stability | Preview/beta vs. stable release |
| System compatibility | How easily does it integrate with current AI-CEO Framework? |
| Content value | Could this become an article or book topic? |
30+ points -> Recommend adoption 20-29 points -> Consider 19 or below -> Skip
Workflow
Periodic Check (weekly)
1. Run `claude --version` to check current version
2. Compare with last checked version
3. If new features found:
a. Research feature details
b. Score on 5 dimensions
c. Create adoption proposal for features scoring 30+
d. Notify CEO
4. Record results in .company/departments/dev/upgrade-log.md
Adoption Execution
1. After proposal is approved (or auto-approve policy applies)
2. Update existing scripts, agents, and skills
3. Run tests
4. Report completion (update STATE.md)
Features to Watch
| Category | Current Usage | Upgrade Opportunity |
|---|---|---|
| Hooks | Basic event-driven | New hook event types |
| Skills | Defined skills | New skill capabilities (args, chaining) |
| MCP | External tool integration | New MCP servers, protocol extensions |
| Agent Teams | Not yet used | Multi-agent coordination |
| Dispatch | Not yet used | Mobile task delegation |
| Remote Control | Not yet used | Remote operations |
| Model updates | Current model | Performance improvements |
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.
- today First seen · 75 lines · 0 tokens per session scan A 62a92d3458c1
upgrade-automation is a skill published in the GitHub repository JOINCLASS/ai-ceo-framework (55 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 565 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-09-26.
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…