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/kastheco/claude-plugins/opencodenpx skills add kastheco/claude-plugins --skill opencodegit clone --depth 1 https://github.com/kastheco/claude-pluginsWhat 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.00080 | $0.00796 |
| Opus 5 | $0.00040 | $0.00398 |
| Sonnet 5 | $0.00016 | $0.00159 |
| Haiku 4.5 | $0.00008 | $0.00080 |
Grade A, and why
specup 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 yesterday.
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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specup — ClickUp + spec-kitty Bridge
Bidirectional bridge between ClickUp task management and spec-kitty feature specifications.
When to activate
- User mentions ClickUp tasks, CU- IDs, or ClickUp URLs
- User wants to create a task in ClickUp
- User wants to turn ClickUp context into a spec-kitty feature spec
- User wants to push a spec-kitty feature spec to ClickUp
Prerequisites
- ClickUp MCP server must be configured and authenticated (see references/setup.md)
- spec-kitty CLI must be installed:
pip install spec-kitty-cli - Run
/specup.setupfirst to verify connectivity and save the default ClickUp Space
Available commands
| Command | Description |
|---|---|
/specup.setup |
Verify ClickUp MCP auth and save default Space for this project |
/specup.new [description] |
Create a ClickUp task from a short interview |
/specup.import <reference> |
Import ClickUp task/list context into a new spec-kitty feature spec |
/specup.export [NNN] |
Export a spec-kitty feature spec to ClickUp as a folder with docs/lists/tasks |
See the individual command files in commands/ for full workflow details.
ClickUp reference parsing
Accept these references in command arguments:
- Task ID:
CU-abc123,#abc123, orabc123 - Task URL:
https://app.clickup.com/t/abc123 - List reference:
list:123456or list URL forms - Multiple references: comma- or space-separated
Normalize task IDs before MCP calls: strip CU-/cu-/# prefixes, extract from URLs.
ClickUp MCP tools
clickup_get_task— fetch task detailsclickup_create_task— create taskclickup_update_task— update task status/metadataclickup_create_task_comment— add commentclickup_create_folder,clickup_create_list— folder/list creation (export)clickup_create_doc— doc creation (export, fall back to tasks if unavailable)
Project config
/specup.setup saves ClickUp workspace info to .specup.json in the project root.
Other commands read this file for the default Space and parent Folder.
If .specup.json is missing when a command needs it, prompt the user to run /specup.setup.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 84 lines · 80 tokens per session scan A 697ff5fbf69e
specup is a skill published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 796 once invoked, about $0.0004 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-31.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…