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/rand/cc-polymath/skillsgit clone --depth 1 https://github.com/rand/cc-polymathWhat 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.00014 | $0.02685 |
| Opus 5 | $0.00007 | $0.01342 |
| Sonnet 5 | $0.00003 | $0.00537 |
| Haiku 4.5 | $0.00001 | $0.00268 |
Grade A, and why
skills 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skills Discovery Assistant
You are helping the user discover and activate relevant skills from their skills library.
Your Task
User's Request: $ARGUMENTS
Follow these steps:
1. Read Skills Catalog
Read the master catalog: Read ../skills/README.md
2. Detect Project Context
Analyze the current directory to understand the project:
# List files to detect project type
ls -la | head -30
# Check for language/framework indicators
ls *.{json,md,go,py,rs,swift,zig,toml,yaml,yml} 2>/dev/null | head -20
Technology Detection → Gateway Mapping:
package.json→ discover-frontend (React, Next.js, TypeScript)go.mod→ discover-api (Go), discover-infrarequirements.txt,pyproject.toml,uv.lock→ discover-api (Python), discover-ml if ML workCargo.toml→ discover-wasm if WASM, discover-api for web servicesbuild.zig→ discover-zig*.swift,*.xcodeproj→ discover-mobile (iOS/Swift)Dockerfile,docker-compose.yml→ discover-infra.beads/→ Beads workflow skills (root level)tests/,__tests__/→ discover-testing- Database files → discover-database
3. Analyze Conversation Context
Review the current conversation for:
- Technologies mentioned (frameworks, tools, databases)
- Problems discussed (performance, debugging, deployment)
- Explicit skill requests
- Work phase (planning, implementation, testing, deployment)
Map to gateway keywords:
- "REST API" → discover-api
- "GraphQL" → discover-api
- "Postgres", "MongoDB", "Redis" → discover-database
- "Docker", "Kubernetes", "Terraform", "AWS", "GCP" → discover-infra
- "CI/CD", "GitHub Actions", "Make", "CMake", "Bazel" → discover-cicd
- "TCP", "HTTP/2", "gRPC", "Nginx", "proxy" → discover-networking
- "debugging", "GDB", "profiling", "logging", "metrics" → discover-debugging
- "caching", "CDN", "Redis cache" → discover-database
- "ML", "model", "training", "Modal" → discover-ml
- "math", "linear algebra" → discover-math
- "compiler", "parser", "AST", "eBPF", "Z3", "Lean" → discover-systems-theory
- "diagram", "flowchart", "Mermaid" → discover-engineering
- "MCP", "MCP server", "tool protocol" → discover-mcp
- "agent", "agentic", "tool use", "task decomposition" → discover-agentic
- "WebSocket", "SSE", "CRDT", "consensus" → discover-distributed
- "product", "roadmap", "collaboration", "GitHub workflows" → discover-product
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 · 327 lines · 0 tokens per session scan A 62e92ffcdd9c
skills is a command published in the GitHub repository rand/cc-polymath (135 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 2,685 once invoked, about $0.0001 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-30.
Other commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
marketing
Command "marketing" from Infrasity-Labs/dev-gtm-claude-skills, covering seo & discoverability, content & copy, demand gen & growth, lifecycle & retention and research & competitive.
verify
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
triage
Triage review findings one by one — present pending TODOs for user decision (approve, skip, modify).
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.