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/ntaffzii/skill-agents/deprecatednpx skills add ntaffzii/Skill-Agents --skill deprecatedgit clone --depth 1 https://github.com/ntaffzii/Skill-AgentsWrote 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/ntaffzii/skill-agents/deprecated)<a href="https://agentmods.dev/skills/ntaffzii/skill-agents/deprecated"><img src="https://agentmods.dev/badge/skills/ntaffzii/skill-agents/deprecated.svg" alt="Measured on agentmods" 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 | $0.00050 | $0.00439 |
| Opus 5 | $0.00025 | $0.00219 |
| Sonnet 5 | $0.00010 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
deprecated 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 4d 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.
What it actually says
Deprecated Skill Maintenance
Use this skill when a skill is no longer recommended but should remain understandable.
Purpose
skills/deprecated/ keeps retired skills visible until users and workflows have moved away from them. Deprecation should explain what replaced the skill and why.
When To Deprecate
- Another skill fully replaces it.
- The workflow is unsafe or misleading.
- The scope became too broad or unclear.
- The domain changed and the instructions are stale.
- It was an experiment that should not be promoted.
Rules
- Do not delete a retired skill until replacements and references are clear.
- Do not leave active workflows pointing at deprecated skills.
- Keep the deprecation reason short and factual.
- Preserve useful reference material when it can be safely reused.
Workflow
-
Identify replacement
- Name the new skill or workflow if one exists.
- If no replacement exists, state that clearly.
-
Move carefully
- Move the old skill folder into
skills/deprecated/. - Keep its
SKILL.mdreadable. - Add a deprecation note near the top.
- Move the old skill folder into
-
Update references
- Remove it from README stable skill lists.
- Remove it from workflow recommendations.
- Update
data/workflows.jsonordata/tools.jsonif needed.
-
Explain the reason
- State why the skill was retired.
- State what to use instead.
- Preserve any useful reference links.
-
Validate
- Run skill and workflow validation.
- Confirm no active workflow depends on the deprecated skill.
Deprecation Note Template
## Deprecated
Status: Deprecated
Reason: ...
Use instead: `replacement-skill`
Date: YYYY-MM-DD
Output Format
End with:
- Deprecated skill
- Replacement
- References updated
- Validation result
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 73 lines · 50 tokens per session scan A 67cef33fbc81
deprecated is a skill published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 439 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-31.
Other skills, from other repositories
geo-platform-optimizer
Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually.
release
Prepare, validate, and publish a Pake release. Not for version bumps without release intent.
pake
Package any website or local web build into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website or a local dist/ folder, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or…
deep-review
Multi-dimensional code review. Use when the user asks to review, evaluate, or audit a PR, diff, branch, or pasted change — including informal review asks like "look at this change for problems" — via light mode: one independent reviewer against the dimension quick checklists. Not for explain-only questions about what…
acceptance
End-to-end verification and self-evidence for a delivery in any repository, with or without a preconfigured verify plan. Discover an existing plan when one was handed to this run; otherwise author checks and publish a standalone acceptance. Pick the proving surface (CLI / web / desktop / iOS Simulator), drive the real…
data-fetching-architecture
LobeHub data-fetching pipeline guide. Use for service layer, Zustand store, SWR, lambdaClient, useClientDataSWR, useFetchXxx hooks, or migrating useEffect fetches.