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/tentacleopera/switchboard/clickup-attachnpx skills add TentacleOpera/switchboard --skill clickup-attachgit clone --depth 1 https://github.com/TentacleOpera/switchboardWrote 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/tentacleopera/switchboard/clickup-attach)<a href="https://agentmods.dev/skills/tentacleopera/switchboard/clickup-attach"><img src="https://agentmods.dev/badge/skills/tentacleopera/switchboard/clickup-attach.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.00000 | $0.00377 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
clickup-attach 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 4d 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.
What it actually says
Attach File to ClickUp Task
When to Use
- User asks to attach a file to a task
- Need to upload screenshots, documents, or other files
Prerequisites
- VS Code setting
switchboard.apiTokenconfigured - File must be under 10MB
- Allowed types: .png, .jpg, .jpeg, .gif, .pdf, .txt, .md, .json
Usage
CUR="$PWD"
while [ "$CUR" != "/" ] && [ ! -d "$CUR/.agents/skills" ]; do CUR=$(dirname "$CUR"); done
source "$CUR/.agents/skills/_lib/sb_api_call.sh"
# Encode file as Base64 (macOS/Linux)
FILE_BASE64=$(base64 -i "./screenshot.png" | tr -d '\n')
sb_api_call POST "/task/clickup/$TASK_ID/attach" \
-H "Content-Type: application/json" \
-d "{
\"fileName\": \"screenshot.png\",
\"fileDataBase64\": \"$FILE_BASE64\",
\"comment\": \"Screenshot of issue\"
}"
Parameters
- fileName (required): Name of the file with extension
- fileDataBase64 (required): Base64-encoded file content
- comment (optional): Comment to accompany attachment
Response
{
"success": true,
"url": "https://...",
"fileName": "screenshot.png",
"size": 12345
}
Error Handling
- 400: Invalid file type or missing fields
- 401: Unauthorized
- 413: File too large (>10MB)
- 503: ClickUp service unavailable
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.
- 4d ago First seen · 50 lines · 0 tokens per session scan A 3304ce637ced
clickup-attach is a skill published in the GitHub repository TentacleOpera/switchboard (213 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 377 tokens. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…