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 spideynolove/claude-dotfiles --skill skillnetgit clone --depth 1 https://github.com/spideynolove/claude-dotfilesWrote 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/spideynolove/claude-dotfiles/skillnet)<a href="https://agentmods.dev/skills/spideynolove/claude-dotfiles/skillnet"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/skillnet/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/spideynolove/claude-dotfiles/skillnet"><img src="https://agentmods.dev/badge/skills/spideynolove/claude-dotfiles/skillnet.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.00041 | $0.01436 |
| Opus 5.5 | $0.00016 | $0.00574 |
| Sonnet 5.5 | $0.00008 | $0.00287 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
skillnet 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skillnet
SkillNet is the npm for AI agent skills. Search 400k+ community skills, install them into any local CLI, create new skills from repos/docs/prompts, and evaluate quality with 5-dimension scoring.
Usage
/skillnet search <query> # semantic search community registry
/skillnet search <query> --mode vector # AI semantic search (more precise)
/skillnet download <url> # install skill package (prompts for target CLI)
/skillnet download <url> --for claude # install to ~/.claude/skills/
/skillnet download <url> --for codex # install to ~/.codex/skills/
/skillnet download <url> --for opencode # install to ~/.opencode/skills/
/skillnet download <url> --for all # install to all three CLIs
/skillnet create --github <url> # auto-create skill from GitHub repo (needs API key)
/skillnet create --prompt "<description>" # generate skill from natural language (needs API key)
/skillnet create --office <file.pdf> # extract skill from PDF/PPT/Word (needs API key)
/skillnet evaluate <path> # 5D quality score: safety/completeness/exec/maintainability/cost
/skillnet analyze <dir> # build relationship graph across all local skills
CLI Directories
| CLI | Skills directory |
|---|---|
| claude | ~/.claude/skills/ |
| codex | ~/.codex/skills/ |
| opencode | ~/.opencode/skills/ |
| dotfiles | ~/Documents/claude-dotfiles/.claude-global/skills/ |
What You Must Do When Invoked
Always activate the venv and load credentials before running skillnet commands:
source ~/.secrets
source ~/env/.venv/bin/activate
API_KEY=$OPENROUTER_API_KEY BASE_URL=https://openrouter.ai/api/v1 SKILLNET_MODEL=openai/gpt-4o skillnet <command>
Search and download need no API key. Create/evaluate/analyze require it.
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 · 138 lines · 41 tokens per session scan A cde830a07c4d
skillnet is a skill published in the GitHub repository spideynolove/claude-dotfiles (2 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 1,436 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-08-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…