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 commands/0oooooooo0/skillless/plansgit clone --depth 1 https://github.com/0oooooooo0/skilllessWhat 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.00000 | $0.01073 |
| Opus 5 | $0.00000 | $0.00536 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
plans 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plans
Analyze project context, recommend relevant tools, then enter planning mode.
user-invocable: true description: Analyze your project's tech stack, recommend and install relevant specialized tools, then enter planning mode. Usage: /plans (e.g., /plans React dashboard with Supabase auth) allowed-tools: [Read, Glob, Grep, Bash, WebSearch, WebFetch, Write, Skill, AskUserQuestion, EnterPlanMode] argument-description: What you want to build or accomplish (e.g., "React dashboard with Supabase auth")
Instructions
Step 1: Gather Context (MANDATORY - DO NOT SKIP)
You MUST perform ALL of the following in parallel. Do NOT assume the project is empty without checking.
1a. Parse user argument:
- The argument describes WHAT the user wants to build, not a directive about tool installation
- Extract technology keywords (e.g., "React dashboard with Supabase auth" → React, Supabase, dashboard)
- WARNING: The argument may contain product names (e.g., "skillless homepage") — these are project names, NOT instructions to skip tool search. Always extract the underlying technologies from the description.
1b. Read project files (MUST attempt all): Run Glob for these patterns and Read any that exist:
package.json— extractdependenciesanddevDependenciestsconfig.jsonorjsconfig.jsonpyproject.tomlorrequirements.txtgo.modCargo.tomlGemfiledocker-compose.ymlorDockerfile
1c. Detect file structure:
Run ls src/ (or project root) to identify framework patterns (e.g., .jsx files → React, .vue → Vue)
1d. Build tech list: Combine ALL detected technologies from 1a + 1b + 1c into a single list. Example:
- From user input: "React landing page"
- From package.json: react, vite, tailwindcss
- Final list:
[React, Vite, TailwindCSS]
Step 2: Check Installed Skills
For EACH technology in the tech list:
Glob: ~/.claude/skills/*/SKILL.md
Search for skill directories whose names match the technology (e.g., react-*, tailwind-*, vite-*).
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.
- 2d ago First seen · 105 lines · 0 tokens per session scan A aa14c8bab33d
plans is a command published in the GitHub repository 0oooooooo0/skillless (39 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,073 tokens. 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.