Borrowing it
Nothing to install: this file belongs to TwoFeetUp/clickup-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TwoFeetUp/clickup-mcp/main/.claude/skills/clickup-delivery/SKILL.mdgit clone --depth 1 https://github.com/TwoFeetUp/clickup-mcpWrote 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/skills/twofeetup/clickup-mcp/clickup-delivery)<a href="https://agentmods.dev/skills/twofeetup/clickup-mcp/clickup-delivery"><img src="https://agentmods.dev/badge/skills/twofeetup/clickup-mcp/clickup-delivery/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/twofeetup/clickup-mcp/clickup-delivery"><img src="https://agentmods.dev/badge/skills/twofeetup/clickup-mcp/clickup-delivery.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00090 | $0.02020 |
| Opus 5 | $0.00045 | $0.01010 |
| Sonnet 5 | $0.00018 | $0.00404 |
| Haiku 4.5 | $0.00009 | $0.00202 |
Grade A, and why
clickup-delivery 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 7d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ClickUp Delivery Skill — TwoFeetUp
Version: 2.0 | Updated: 26 feb 2026 | Space: TwoFeetUp Delivery
Doel van deze skill
Beschrijft hoe TwoFeetUp ClickUp gebruikt voor delivery. Gebruik dit als kennisbron bij:
- Aanmaken of controleren van builds, milestones, features
- Vragen over waar iets hoort in de structuur
- Workflow checks (juiste status, juiste velden, juiste lijst)
- Validatie van wat iemand heeft aangemaakt
Voor velddetails → references/field-requirements.md
Voor lijstregels → references/list-guide.md
Voor beslissingen → references/decisions-log.md
Voor geplande automations → references/automations.md
Voor MCP beperkingen → references/mcp-limitations.md
Space structuur
TwoFeetUp Delivery (Space)
├── Clients (Folder)
│ └── All Clients (List) — één task per klant
├── AI & Automation Solutions (Folder)
│ ├── Scope builds (List) — builds in scoping/on hold
│ ├── Building (List) — actieve development
│ ├── Client Handover (List) — oplevering
│ └── Maintenance (List) — post-oplevering onderhoud
├── Workshops (List)
├── Blueprint Library (List)
└── [overige lijsten]
Hiërarchie (4 niveaus)
Build (= 1 factuur, gekoppeld aan client)
└── Milestone (= oplevermoment aan klant)
└── Feature (= reist door board, primair werkniveau)
└── Taak (= subtask, blijft onder feature)
Regels:
- 1 Build = 1 factuur
- Features zijn de kaartjes op het board — die sleep je door statussen
- Taken zijn subtasks — niet los zichtbaar op board
- Milestones volgen als alle features onder hen DONE zijn
- ~6-9 milestones per build (3 fases × 2-3 iteraties)
- Eerste milestone = kleine MVP voor scope-validatie
Time estimates — belangrijk
Time estimates op features en milestones tellen automatisch op naar hogere niveaus in ClickUp. Regels:
- Estimates horen op feature-niveau
- Zet geen time estimate op een build zelf — ClickUp telt die bij de som op, waardoor de uren cap niet meer klopt
- Als er al estimates op hogere niveaus staan (build of milestone), controleer dan bij het toevoegen van feature-level estimates of de hogere laag naar beneden bijgesteld moet worden
- Is het een verfijning (bestaande estimate opgesplitst)? → hogere laag verlagen
- Is het een toevoeging (extra werk)? → hogere laag kan staan, maar check of het nog binnen uren cap past
- Uren cap bewaken: totaal van feature estimates vs
🧢 Max hours (u). Signalering bij 80%.
What ships with it
13 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.
- references/automations.md 1.8 KB
- references/decisions-log.md 5.4 KB
- references/field-requirements.md 7.8 KB
- references/gap-analysis.md 18 KB
- references/list-guide.md 3.1 KB
- references/mcp-issues-2026-02-26.md 1.2 KB
- references/mcp-issues.md 7.4 KB
- references/mcp-limitations.md 4.2 KB
- references/weekly-2026-02-23.md 15 KB
- references/workflow-build-creation.md 14 KB
- references/workflow-milestone-flows.md 13 KB
- references/workflow-operational.md 8.3 KB
- references/workflow-status-rules.md 7.5 KB
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.
- 7d ago First seen · 218 lines · 90 tokens per session scan A b37a77dba10f
clickup-delivery is a skill published in the GitHub repository TwoFeetUp/clickup-mcp (0 stars, last pushed 4mo ago), licensed MIT. It adds 90 tokens to every session and 2,020 once invoked, about $0.0005 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-09-01.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.