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/kastheco/claude-plugins/specup.importgit clone --depth 1 https://github.com/kastheco/claude-pluginsWrote 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/commands/kastheco/claude-plugins/specup.import)<a href="https://agentmods.dev/commands/kastheco/claude-plugins/specup.import"><img src="https://agentmods.dev/badge/commands/kastheco/claude-plugins/specup.import.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 | $0.00014 | $0.01178 |
| Opus 5 | $0.00007 | $0.00589 |
| Sonnet 5 | $0.00003 | $0.00236 |
| Haiku 4.5 | $0.00001 | $0.00118 |
Grade A, and why
specup.import 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 3d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specup.import $ARGUMENTS
Create a new spec-kitty feature spec from ClickUp context.
Goal
Turn one or more ClickUp references into a high-quality spec.md that is ready for /spec-kitty.plan.
Accepted input
$ARGUMENTS may include:
- Single task:
CU-abc123,#abc123,abc123,https://app.clickup.com/t/abc123 - List reference:
list:123456, list URL forms such as/list/123456or/li/123456 - Multiple references:
CU-a1b2c3, CU-d4e5f6(comma or space separated)
If no argument is provided, ask the user for a ClickUp reference and stop.
Workflow
1) Preflight checks
- Ensure the command runs from a project root where
kitty-specs/is expected. - Ensure
spec-kittyCLI is installed:
spec-kitty --version
If missing, stop and provide:
pip install spec-kitty-cli
2) Parse and normalize ClickUp references
Normalize IDs before MCP calls:
- Strip
CU-/cu- - Strip leading
# - Extract IDs from task URLs
- Detect list references from
list:prefix or list URL patterns
Deduplicate all resolved IDs.
3) Fetch ClickUp context via MCP
- For each task ID, call
clickup_get_task. - For each list reference, use available list MCP tools (for example
clickup_get_list) to resolve task IDs, then hydrate each task withclickup_get_task. - Build a concise context bundle containing:
- task name
- status
- priority
- description
- acceptance/checklist items
- subtasks (if present)
- useful comments (if available)
If list lookup tools are unavailable, ask the user for explicit task IDs and continue.
4) Discovery interview (scope-proportional)
Before writing files, run a short interview:
- Trivial scope: 1-2 questions
- Medium scope: 3-4 questions
- Complex scope: 5+ questions
Cover at least:
- scope boundaries (what is in/out)
- target users and expected outcomes
- constraints and dependencies
- success signals
Then present a short intent summary and confirm with the user.
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.
- 3d ago First seen · 186 lines · 14 tokens per session scan A 9a6bf3c2b552
specup.import is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 1,178 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-31.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.