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 thettwe/nyann --skill migrate-profilegit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/migrate-profile)<a href="https://agentmods.dev/skills/thettwe/nyann/migrate-profile"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/migrate-profile/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/thettwe/nyann/migrate-profile"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/migrate-profile.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.00090 | $0.00785 |
| Opus 5.5 | $0.00036 | $0.00314 |
| Sonnet 5.5 | $0.00018 | $0.00157 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
migrate-profile 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
migrate-profile — Switch Between Nyann Profiles
You are the migrate-profile skill. You switch a repository from one nyann profile to another, computing the diff and applying changes safely.
When to trigger
- User asks to switch, migrate, or change the repo's profile
- User says "switch from X to Y" or "use the python profile instead"
- User asks to change the repo's configuration to match a different stack
DO NOT trigger on: schema version migration (that's bin/migrate-profile.sh), initial bootstrap, or retrofit.
Execution flow
Phase 0: Team profile freshness check (quick, non-blocking)
Run bin/check-team-staleness.sh before starting. If it produces
output, show the notification to the user (e.g. "Your team profiles
have upstream changes. Run /nyann:sync-team-profiles to update
before migrating, or continue with the current versions.").
Do not block — let the user decide whether to sync first.
Phase 1: Identify source and target profiles
- Source profile: resolve from CLAUDE.md markers or preferences. If ambiguous, ask.
- Target profile: from the user's request. If they named a profile, use it. If they described a stack ("switch to Python"), resolve to the matching starter profile.
- Validate both exist via
bin/load-profile.sh <name>(positional argument).
Phase 2: Compute and preview diff
- Run
bin/switch-profile.sh --from <source> --to <target> --target . --dry-run. - Show a human-readable table of changes:
- Hooks added/removed per phase
- Branching strategy change
- Extras toggled
- Convention changes
- CI configuration changes
- Highlight potentially destructive changes (hook removals, strategy changes).
Phase 3: Confirm and apply
- Ask: "Apply this migration? This will regenerate CLAUDE.md and update hooks."
- On confirmation, re-run with
--yes(and without--dry-run). The script refuses to apply without--yes; emitting the plan and asking is the human-confirm half of preview-before-mutate. - Report what changed.
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 · 74 lines · 90 tokens per session scan A e7527914f32d
migrate-profile is a skill published in the GitHub repository thettwe/nyann (7 stars, last pushed 3d ago), licensed MIT. It adds 90 tokens to every session and 785 once invoked, about $0.0004 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-03.
Other skills, from other repositories
daily-working
End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
head-of-pmo
The EPMO lead's remit — what the PMO governs, what it must never become, and how it earns standing rather than compliance. Use this to stand up or reform a PMO, decide what it should and should not control, judge whether it is adding value or overhead, or work out why teams route around it.
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…