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/codenamev/claude_memory/upgrade-dependenciesnpx skills add codenamev/claude_memory --skill upgrade-dependenciesgit clone --depth 1 https://github.com/codenamev/claude_memoryWhat 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.00061 | $0.01485 |
| Opus 5 | $0.00030 | $0.00743 |
| Sonnet 5 | $0.00012 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
upgrade-dependencies 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 3d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Upgrade Skill
Systematically upgrade Ruby gem dependencies by researching latest versions, reviewing release notes for breaking changes, updating version constraints, verifying with tests, and confirming codebase alignment.
The goal is a thoughtful upgrade — not blindly bumping versions, but understanding what changed and ensuring the codebase is compatible. This matters because a silent API change can introduce bugs that tests don't catch if the tests don't exercise the affected code path.
Process Overview
- Discover current dependencies and their constraints
- Research latest versions and release notes (in parallel)
- Analyze breaking changes and codebase impact
- Upgrade version constraints and install
- Verify with the full test suite
- Report a summary table with upgrade details
Step 1: Discover Current Dependencies
Read the gemspec and Gemfile to build a complete dependency inventory.
Read *.gemspec → runtime dependencies (add_dependency)
Read Gemfile → development dependencies (gem declarations)
Run: bundle outdated → current vs latest versions, which are constrained
Build a working list with these columns:
- Gem name
- Source (gemspec or Gemfile)
- Current constraint (e.g.,
~> 5.0) - Installed version (from
bundle outdatedorGemfile.lock) - Latest version (from
bundle outdated) - Constrained? (is the version constraint preventing upgrade?)
Step 2: Research Release Notes
For each gem that has a newer version available, research what changed. Launch these as parallel Agent subagents — one per gem — to avoid sequential delays.
Each research agent should:
- Run
gem search <name> --exact --versionsto confirm the latest version - Fetch the changelog or release notes from GitHub (check CHANGELOG.md, CHANGES, HISTORY.md, or GitHub Releases)
- Summarize changes between the installed version and latest version
- Flag any breaking changes, deprecations, or API changes
- Note if it's a major version bump (higher risk)
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.
- 3d ago First seen · 155 lines · 61 tokens per session scan A 42f6a6d04bc8
upgrade-dependencies is a skill published in the GitHub repository codenamev/claude_memory (24 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,485 once invoked, about $0.0003 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-30.
Other skills, from other repositories
contributing
Contribute to RubyLLM - set up the repo, run and record specs, add providers or chat options, work on the Rails integration, and edit docs. Use when fixing a bug, building a feature, writing specs, or changing documentation in the RubyLLM codebase.
new
Create a new project to start development quickly.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
ruby-conventions
Rootstrap Ruby style conventions. Use when writing, reviewing, or editing any Ruby source file (.rb, .rake, Gemfile, Rakefile, .gemspec, config.ru) to ensure code follows the Rootstrap Ruby style guide — covers layout, syntax, naming, classes/modules, exceptions, collections, strings, regexes, metaprogramming, and…
linkyee-plugin-builder
Use when the user wants to add dynamic data (GitHub stars, latest blog posts, weather, follower counts, repo activity, anything fetched from a URL) to their linkyee site by writing a build-time plugin. Triggers on phrases like "add a plugin", "show my latest Medium post on the page", "fetch X and display it", "make…