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 agentmods add skills/bostonorange/claude-code-framework/ai-updatenpx skills add BostonOrange/claude-code-framework --skill ai-updategit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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 | $0.00034 | $0.00484 |
| Opus 5 | $0.00017 | $0.00242 |
| Sonnet 5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
ai-update 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 yesterday.
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.
What it actually says
AI Update
Create a feature branch and open a PR for AI process/tooling changes.
Usage
/ai-update # Auto-detect changed AI files
/ai-update "add validate skill" # With a description
Scope
AI process files:
| Path | Content |
|---|---|
CLAUDE.md |
Project-level instructions |
.claude/skills/*/SKILL.md |
Skill definitions |
.claude/skills/*/references/*.md |
Skill references |
.claude/skills/*/examples/*.md |
Skill examples |
.claude/settings.json |
Claude Code settings |
Process
1. Identify Changes
git status --short
Filter to AI-scoped paths. If no AI files changed, stop.
2. Create Branch
Branch naming: ai/{short-description}
git fetch origin {{BASE_BRANCH}}
git checkout -b ai/{slug} origin/{{BASE_BRANCH}}
3. Stage AI Files
Stage only AI-scoped files:
git add CLAUDE.md
git add .claude/skills/
4. Commit
chore(ai): {short description}
{bullet list of changes}
5. Push & Create PR
git push -u origin ai/{slug}
gh pr create --base {{BASE_BRANCH}} --assignee @me \
--title "chore(ai): {description}" \
--body "$(cat <<'EOF'
## Summary
- {changes}
## Files Changed
- {list}
EOF
)"
Edge Cases
| Scenario | Behavior |
|---|---|
| No AI files changed | Stop, inform user |
| Mixed AI + code changes | Stage only AI files, warn about unstaged code |
Already on ai/* branch |
Reuse it |
Related Skills
/add-reference— add knowledge docs (often shipped via this skill)/validate— code validation (often shipped via this skill)
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.
- yesterday First seen · 93 lines · 34 tokens per session scan A 625f1ffb2b4a
ai-update is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 484 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…