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.exportgit 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.00020 | $0.01919 |
| Opus 5 | $0.00010 | $0.00959 |
| Sonnet 5 | $0.00004 | $0.00384 |
| Haiku 4.5 | $0.00002 | $0.00192 |
Grade A, and why
specup.export 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specup.export $ARGUMENTS
Export a local spec-kitty feature spec to ClickUp, creating a folder with docs, lists, and tasks. Idempotent: re-running updates existing items instead of creating duplicates.
Accepted input
$ARGUMENTS is a fuzzy feature identifier:
- Feature number:
011,11,11- - Partial slug:
mcp-agent,agent-swarm - Full slug:
011-mcp-agent-swarm-orchestration - Empty: list available features and ask
Workflow
1) Resolve feature directory
- List all directories under
kitty-specs/. - Fuzzy-match
$ARGUMENTSagainst directory names:- Numeric prefix match:
011matches011-mcp-agent-swarm-orchestration - Substring match:
agent-swarmmatches011-mcp-agent-swarm-orchestration
- Numeric prefix match:
- If zero matches: stop, list available features.
- If multiple matches: present candidates and ask user to pick one.
- Set
FEATURE_DIRto the resolved absolute path.
2) Load feature artifacts
Read from FEATURE_DIR:
| File | Required | ClickUp target |
|---|---|---|
meta.json |
yes | Folder name and metadata |
spec.md |
yes | Doc: Specification |
plan.md |
no | Doc: Implementation Plan |
research.md |
no | Doc: Research |
data-model.md |
no | Doc: Data Model |
quickstart.md |
no | Doc: Quickstart |
tasks.md |
no | Reference for WP overview |
tasks/WP*.md |
no | List items (one task per WP) |
checklists/*.md |
no | Checklist items on a task |
contracts/*.json |
no | Attached or inlined in a doc |
If meta.json is missing, stop with an error.
3) Load or create sync tracking file
Check for FEATURE_DIR/.specup-sync.json. This file tracks ClickUp IDs for idempotent updates:
{
"folder_id": null,
"space_id": null,
"docs": {},
"lists": {},
"tasks": {},
"last_synced": null
}
If the file exists, load it. If not, initialize an empty tracking structure.
4) Determine ClickUp destination
Resolve the target Space (and optional parent Folder) in this order:
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 · 192 lines · 20 tokens per session scan A 83ded746eab7
specup.export is a command published in the GitHub repository kastheco/claude-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 1,919 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
git
Git operations with intelligent commit messages and workflow optimization.
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.