Borrowing it
Nothing to install: this file belongs to flowing-abyss/obsidian-hybrid-search. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/flowing-abyss/obsidian-hybrid-search/master/.ai/skills/deprecation-and-migration/SKILL.mdgit clone --depth 1 https://github.com/flowing-abyss/obsidian-hybrid-searchWrote 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/flowing-abyss/obsidian-hybrid-search/deprecation-and-migration)<a href="https://agentmods.dev/skills/flowing-abyss/obsidian-hybrid-search/deprecation-and-migration"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/deprecation-and-migration/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/flowing-abyss/obsidian-hybrid-search/deprecation-and-migration"><img src="https://agentmods.dev/badge/skills/flowing-abyss/obsidian-hybrid-search/deprecation-and-migration.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.00060 | $0.01050 |
| Opus 5.5 | $0.00024 | $0.00420 |
| Sonnet 5.5 | $0.00012 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
deprecation-and-migration 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deprecation and Migration
Where this sits in the workflow
This skill is an entry point parallel to skill:brainstorming for removal- or
migration-shaped requests , it is not an alternative to skill:brainstorming and
skill:writing-plans, and it does not go straight to implementation.
removal or migration request
→ deprecation-and-migration (this skill: contract analysis and migration constraints)
→ brainstorming (design approval, using this skill's output as input)
→ writing-plans
→ implementation
→ verification
Use this skill first to answer the five questions below. Then hand that to
skill:brainstorming as the input for design approval, same as any other
spec input , do not skip straight from this skill's decision to writing code.
When to use
Only when the change touches an external or persisted contract:
- the format of persisted configuration or SQLite data
- public CLI flags, MCP tools and result schemas, or package exports
- a user-facing setting or feature that needs a compatibility path so existing users aren't broken by the change
- a dependency/API migration that affects stored data or user-visible behavior
Not this skill:
- removing internal dead code
- private refactoring with no external contract change
- renaming an internal function
- swapping an implementation while keeping the same external contract
- deleting an unused file
The five questions
Answer all five before handing off to skill:brainstorming:
- What contract or persisted data is changing? Name it exactly (a settings field, a command id, a public method).
- What could already depend on the old form? Existing users' saved configuration, CLI scripts, MCP clients, and package consumers.
- Does this need an automatic migration, or a compatibility fallback? If old data needs transforming, when does that run (on load)? If old behavior needs to keep working for a while, what's the fallback?
- What happens on rollback? If the user reverts to an older package version after this ships, does their data still load?
- When is it safe to remove the old form? What has to be true first (a released version where the new form has existed for at least one version, so a rollback within that window still works)?
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 · 98 lines · 60 tokens per session scan A 13d882466765
deprecation-and-migration is a skill published in the GitHub repository flowing-abyss/obsidian-hybrid-search (113 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,050 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-10-24.
Other skills, from other repositories
patent-docket
A workflow coordinator for patent case files, from an inventor's technical disclosure to patent application documents. A patent docket is the tracked record of a patent matter, including its stage, questions, drafts, and handoffs.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
codemark
Manage structural code bookmarks that survive refactoring. Use when the user says "remember this", "bookmark this", "save this location", "load my bookmarks", "what do I have bookmarked", "mark this code", "codemark", or when starting a new session and needing to reload context from a previous session. Also use…
palaia-memory
Check this person's shared memory before answering anything about their own work, and add to it when something is worth keeping. It holds their projects, decisions and reasons, house conventions (naming, commit messages, tests, releases, review and escalation), people and hard-won details, and every AI tool they use…
Honesty Check
Run the volunteering ledger before declaring work done. Forces surfacing of what changed/didn't, what was noticed-but-not-fixed, what was guessed, and what tradeoffs were made on the principal's behalf. The standard - the principal should never be surprised later by something the agent knew at the time.
palaia-messenger
Register this session with the shared directory so other AI sessions and this person's dashboard can see what you are doing, then use it to reach another live session directly instead of relaying everything through the person. Use it at the start of a task, before picking one up, when your work depends on or informs…