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 aiocean/claude-plugins --skill aio-skillifygit clone --depth 1 https://github.com/aiocean/claude-pluginsWrote 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/aiocean/claude-plugins/aio-skillify)<a href="https://agentmods.dev/skills/aiocean/claude-plugins/aio-skillify"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-skillify/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/aiocean/claude-plugins/aio-skillify"><img src="https://agentmods.dev/badge/skills/aiocean/claude-plugins/aio-skillify.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.00023 | $0.01461 |
| Opus 5.5 | $0.00009 | $0.00584 |
| Sonnet 5.5 | $0.00005 | $0.00292 |
| Haiku 4.5 | $0.00002 | $0.00146 |
Grade A, and why
aio-skillify 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skillify - Capture Session Workflows as Reusable Skills
Turn what you just did into a skill that works every time.
Goal
Analyze the current session, interview the user about their intent, and produce a well-structured SKILL.md file that captures the repeatable process.
Steps
1. Load Session Memory
Session memory is stored at ~/.claude/projects/{sanitized-cwd}/{sessionId}/session-memory/summary.md where sanitized-cwd replaces all non-alphanumeric characters with -.
Use Glob to find and Read the most recent session memory for the current project. This gives you a compact summary of the entire session including compacted context. If no session memory exists, skip this step and rely on the current conversation context.
2. Analyze the Session
Combine the session memory with the current conversation to identify:
- What repeatable process was performed
- What the inputs/parameters were
- The distinct steps (in order)
- The success artifacts/criteria for each step (e.g. not just "writing code" but "an open PR with CI fully passing")
- Where the user corrected or steered you - these are gold for capturing preferences
- What tools and permissions were needed
- What agents were used (if any)
3. Interview the User
Use AskUserQuestion for ALL questions. Never ask via plain text. For each round, iterate until the user is happy. Always include a freeform "Other" option - do NOT add your own "Needs tweaking" option.
Round 1: High-level confirmation
- Suggest a name and description for the skill based on your analysis
- Suggest high-level goal(s) and specific success criteria
Round 2: Details
- Present the high-level steps as a numbered list. Tell the user you will dig into details next round.
- If the skill needs arguments, suggest them based on what you observed.
- Ask if this skill should run
inline(in current conversation, user can steer mid-process) orfork(sub-agent with own context, better for self-contained tasks). - Ask where to save. Suggest a default based on context:
- This repo (
.claude/skills/<name>/SKILL.md) - for workflows specific to this project - Personal (
~/.claude/skills/<name>/SKILL.md) - follows you across all repos - Plugin (
<plugin-path>/skills/<name>/SKILL.md) - if part of a plugin
- This repo (
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 · 148 lines · 23 tokens per session scan A 07f200b6865d
aio-skillify is a skill published in the GitHub repository aiocean/claude-plugins (4 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 1,461 once invoked, about $0.0001 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
eval-hooks
Audit Claude Code and Codex hooks for validity, safety, and correctness across settings.json, hooks.json, config.toml, plugin, and skill or agent frontmatter hooks. Resolves each command, checks event names, handler types, matchers, exit-code and JSON decision strategy, and timeouts against each host's documented…
eval-skills
Audit a project or library of skills for metadata, trigger boundaries, workflow completion criteria, local resource closure, instruction economy, tool scope, effort, and routing evidence. Use before shipping skills, after importing a skill collection, or when a skill triggers too often or not at all.
source-command-audit-whitepapers
Audit version freshness, FR/EN parity, and metadata quality of all whitepapers and recap cards.
audit-agents-skills
Audit Claude Code agents, skills, and commands for quality and production readiness. Use when evaluating skill quality, checking production readiness scores, or comparing agents against best-practice templates.
design-patterns
Detect, suggest, and evaluate GoF design patterns in TypeScript/JavaScript codebases. Use when refactoring code, applying singleton/factory/observer/strategy patterns, reviewing pattern quality, or finding stack-native alternatives for React, Angular, NestJS, and Vue.
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…