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/axgord/claude-workflow/skill-managernpx skills add AxGord/claude-workflow --skill skill-managergit clone --depth 1 https://github.com/AxGord/claude-workflowWrote 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/axgord/claude-workflow/skill-manager)<a href="https://agentmods.dev/skills/axgord/claude-workflow/skill-manager"><img src="https://agentmods.dev/badge/skills/axgord/claude-workflow/skill-manager.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.1 | $0.00011 | $0.02957 |
| Opus 5 | $0.00005 | $0.01478 |
| Sonnet 5 | $0.00002 | $0.00591 |
| Haiku 4.5 | $0.00001 | $0.00296 |
Grade B, and why
skill-manager scanned grade B with 1 finding 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 6d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls ~/.claude/skills/ How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill lifecycle manager
This skill is HEAVY. Always run via subagent (Task tool), never in main context.
Model policy
- Use Opus or Sonnet for subagents
- NEVER use Haiku — insufficient for quality work
- Skills are optimized for Opus/Sonnet reasoning capabilities
Model selection by task:
- OPTIMIZE skills → Sonnet (filtering/editing, doesn't need deep reasoning)
- CREATE skill from research → Sonnet (research + writing)
- Complex code generation → Opus (when quality is critical)
⛔ PROTECTED skills — NEVER modify or overwrite
Skills matching preferences* (preferences/, preferences-<lang>/,
any other preferences-* variant) are user-owned personal rules.
These are ONLY updated when the user gives direct feedback. skill-manager must NEVER touch, overwrite, or regenerate them without an explicit user request.
1. FIND an existing skill
Search order:
A) Check awesome-agent-skills: https://github.com/VoltAgent/awesome-agent-skills
B) Check awesome-claude-code: https://github.com/hesreallyhim/awesome-claude-code
C) Check anthropics/skills: https://github.com/anthropics/skills
D) Search npm: npm search claude skill <keyword>
E) Search GitHub: gh search repos "claude skill <keyword>"
IMPORTANT: Subagents don't have access to skills. When launching a research subagent, include these web-reading rules in the prompt:
- For GitHub repos/issues/PRs → use
ghCLI, not web fetch - Fetch web pages via Jina Reader:
WebFetch("https://r.jina.ai/<url>", "<precise extraction prompt>") - If Jina fails → direct
WebFetchwith prompt: "Extract ONLY main article content as clean markdown. Ignore navigation, sidebars, headers, footers, ads." - If page inaccessible →
WebSearchfor mirrors, docs, cached versions - ALWAYS specify exactly what to extract — never "get the page" or "summarize"
2. INSTALL an existing skill
# From known repos
npx -y openskills install <owner/repo/skill-name> -g
# Or manually
# 1. Fetch the SKILL.md content
# 2. Write to ~/.claude/skills/<skill-name>/SKILL.md
# 3. Copy any scripts/, references/, assets/ if present
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.
- 6d ago First seen · 288 lines · 11 tokens per session scan B 192e8dc864f9
skill-manager is a skill published in the GitHub repository AxGord/claude-workflow (5 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,957 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…