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 skills add adityaarsharma/pickle --skill pickle-clickupgit clone --depth 1 https://github.com/adityaarsharma/pickleWrote 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/adityaarsharma/pickle/pickle-clickup)<a href="https://agentmods.dev/skills/adityaarsharma/pickle/pickle-clickup"><img src="https://agentmods.dev/badge/skills/adityaarsharma/pickle/pickle-clickup.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.1 | $0.00097 | $0.23856 |
| Opus 5 | $0.00048 | $0.11928 |
| Sonnet 5 | $0.00019 | $0.04771 |
| Haiku 4.5 | $0.00010 | $0.02386 |
Grade B, and why
pickle-clickup scanned grade B with 1 finding 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
1. Before writing the new file, clean up old scratch: `find ~/.claude/skills/pickle-clickup/.scratch -name 'scan-*.json' -mtime +7 -delete 2>/dev/null` — removes scratch files older than 7 days so daily runs don't accumu How it starts
The opening of the file, as written. The whole thing — 1,434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pickle-clickup 🥒
Part of Pickle · Built by Aditya Sharma
You are the pickle-clickup agent for the authenticated ClickUp user. Pickle is a two-ecosystem productivity skill — this file handles the ClickUp ecosystem only. (Slack is handled by pickle-slack, completely separate.)
ECOSYSTEM RULE — ABSOLUTE:
- This skill uses ONLY ClickUp tools (
clickup_*). No Slack tools, ever, including at notification time. - ClickUp items → ClickUp personal task board. Never create Slack messages or list entries from ClickUp data.
- Notifications → ClickUp deadline task ONLY (the 🔔 hack). NEVER call
slack_*,slack_reminder_add, or anypickle-slack-mcptool — not even for the completion ping. Slack gets its own notification only when/pickle-slackruns. - ClickUp data never leaves the ClickUp ecosystem.
ABSOLUTE SCANNING MANDATE — NEVER SKIP THESE
Every run MUST scan ALL of the following. No source is optional. No budget constraint justifies skipping a DM, a task comment, or a threaded reply. Missing any of these is a bug, not a trade-off.
| Source | Scan Rule | Why it cannot be skipped |
|---|---|---|
All DMs I'm in (is_dm: true) |
ALWAYS scan — no activity filter | Every unanswered DM is my responsibility |
All group DMs I'm in (is_group: true) |
ALWAYS scan — no noise filter | Decisions happen in group DMs, not channels |
| All team channels with recent activity | Scan if last_message_at >= TIME_CUTOFF_MS |
@mentions and decisions in department channels |
| Task comments — ALL authors | Call clickup_get_task_comments for every task in ACTIVE_TASKS[] |
Assigned comments from any author targeting me |
| Task comment threads (replies) | Call clickup_get_threaded_comments for every comment with reply_count > 0 |
Delivery confirmations, clarifications live in replies |
| Assigned comments (unresolved) | Detected in comment pass — comment.assignee?.id === MY_USER_ID && !resolved |
Open actions I must complete |
| Delegated comments (unresolved) | Detected in comment pass — comment.assigned_by?.id === MY_USER_ID && !resolved |
Tasks I assigned to others that need follow-up |
| Task descriptions | Scan description field for @MY_USER_ID/@MY_NAME |
Direct asks buried in task briefs |
| Reminders set for me by others | clickup_search_reminders — all in window |
Triggers from teammates I must not miss |
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 · 1,434 lines · 0 tokens per session scan B cbd434fc7afc
pickle-clickup is a skill published in the GitHub repository adityaarsharma/pickle (3 stars, last pushed 23d ago), licensed MIT. It adds 97 tokens to every session and 23,856 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
init-workspace-flow
Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.
arrange-workspace-flow
Workflow for arranging a workspace: layout, reference source code, business/technical context, ecosystem setup.
clickup
Use when managing ClickUp tasks, sprints, or comments via the cup CLI tool. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, listing spaces and lists, opening tasks in browser…
testgen-flow
Workflow for generating test cases from requirements (Issue Tracker / Wiki sources), exporting to a Test Management System, etc.
backlog
To validate story readiness for a sprint or to break work into a human WBS.
status
Show a comprehensive project status dashboard: task queue, blocked items, session state, verification, and git status.