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 viknesh20-20/claude-code-tool-kit --skill migrate-frameworkgit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/migrate-framework)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/migrate-framework"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/migrate-framework/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/viknesh20-20/claude-code-tool-kit/migrate-framework"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/migrate-framework.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.00056 | $0.00624 |
| Opus 5.5 | $0.00022 | $0.00250 |
| Sonnet 5.5 | $0.00011 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
migrate-framework 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 1mo 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Migration Assistant
Detect Current Setup
!ls package.json requirements.txt go.mod Cargo.toml *.csproj Gemfile composer.json 2>/dev/null
!cat package.json 2>/dev/null | head -30
!find . -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" -o -name "*.py" -o -name "*.go" -o -name "*.rs" \) -not -path "*/node_modules/*" -not -path "*/.git/*" 2>/dev/null | head -30
Migration Process
Step 1: Audit Current Usage
- Identify all imports/requires of the source framework
- Map which features and APIs are used
- Catalog plugins, middleware, and extensions in use
- Count affected files and estimate scope
Step 2: Map Source to Target
For each source feature in use, determine:
| Source API | Target Equivalent | Breaking Change? | Notes |
|---|---|---|---|
| ... | ... | Yes/No | ... |
Flag features with NO direct equivalent — these need custom solutions.
Step 3: Migration Plan
Create an ordered migration plan:
- Setup: Install target framework alongside source (coexistence period)
- Configuration: Migrate config files (build config, env, plugins)
- Core: Migrate entry points and routing
- Components/Modules: Migrate individual files (ordered by dependency — leaves first)
- Tests: Update test setup and migrate test files
- Cleanup: Remove source framework dependencies
Step 4: File-by-File Migration Order
List every file that needs changes, ordered by:
- No dependencies on other migrated files (migrate first)
- Shared utilities and types
- Core modules
- Feature modules
- Entry points (migrate last)
Step 5: Execute Migration
For each file:
- Show the current code
- Show the migrated code
- Explain what changed and why
- Run tests after each file to catch regressions
Rules
- Migrate incrementally — one file or module at a time
- Keep both frameworks running during migration if possible
- Run tests after every change
- Don't change functionality during migration — only change the framework layer
- Flag any features that cannot be migrated 1:1
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.
- 1mo ago First seen · 63 lines · 56 tokens per session scan A e15aa3e71bc7
migrate-framework is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 56 tokens to every session and 624 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-08-31.
Other skills, from other repositories
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.