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/joaoequer/oficina/clickup-task-breakdownnpx skills add JoaoEquer/Oficina --skill clickup-task-breakdowngit clone --depth 1 https://github.com/JoaoEquer/OficinaWrote 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/joaoequer/oficina/clickup-task-breakdown)<a href="https://agentmods.dev/skills/joaoequer/oficina/clickup-task-breakdown"><img src="https://agentmods.dev/badge/skills/joaoequer/oficina/clickup-task-breakdown.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.00077 | $0.00703 |
| Opus 5 | $0.00039 | $0.00351 |
| Sonnet 5 | $0.00015 | $0.00141 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
clickup-task-breakdown 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 5d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
From scope documents to ClickUp tasks
Process for converting a project's planning documents into an executable backlog, without inventing scope.
Rule number one: source of truth
Tasks are born exclusively from the project's source documents — typically three:
- Data model (UML/entity diagram)
- Functional proposal (what the system does, from the product view)
- Execution plan (modules, hours, sequence)
If something isn't in any document, it doesn't become a task — it becomes a question for the tech lead. Generating tasks from imagined scope is the most expensive mistake in this process.
Structure
- Parent task = module from the execution plan. One to one. If the plan has 7 modules, there are 7 parent tasks.
- Subtask = verifiable deliverable within the module (3–6 per module is normal). "Verifiable" = you can look at it and say whether it's done.
- Each subtask carries:
- Title: infinitive verb + object ("Implement task CRUD", "Set up CI pipeline")
- "How to" description: 3–8 lines grounded in the project's locked technical decisions — not a generic tutorial
- Estimate inherited/apportioned from the module's hours in the plan
- Assignee when team allocation is already known
Sequencing and dependencies
Build the dependency graph between modules BEFORE distributing work (e.g. Setup → Auth → domains in parallel → dashboards → QA). In ClickUp, use waiting on relations between parent tasks; within a module, the subtask order already expresses the sequence.
Deliver alongside it a half-page sequencing guide: the order, the why, and where the team can parallelize.
Import
For volume (20+ tasks), generate a CSV in ClickUp's Spreadsheet Importer format:
Task Name,Parent Task,Description,Time Estimate,Assignee
"Module A — Authentication and org structure",,"...",30h,
"Implement JWT login","Module A — Authentication and org structure","How to: ...",8h,John
Gotchas that have already caused rework:
Parent Taskreferences the exact name of the parent task (case-sensitive)- Descriptions containing commas/line breaks go inside double quotes
- Estimates in the format the importer accepts (
8h, not8 hours) - No decorative Unicode characters (borders, emoji overload) — they break rendering in several places
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.
- 5d ago First seen · 59 lines · 77 tokens per session scan A 5ea3604f9a9b
clickup-task-breakdown is a skill published in the GitHub repository JoaoEquer/Oficina (2 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 703 once invoked, about $0.0004 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 skills, from other repositories
openrig-user
Use when a specific rig command, subcommand, or flag is already known and you need its exact syntax, JSON shape, defaults, or error meaning. NOT for natural capability discovery, open-ended how-do-I questions, or choosing which OpenRig move applies.
forming-an-openrig-mental-model
Use when the system around you does not make sense yet: you just booted into a seat and do not know how the pieces fit; someone said rig, pod, seat, fleet, topology, or slice and you are not certain what they mean here; you are unsure what kind of rig you are in or what it is for; you do not know how skills reach you…
orienting-to-an-inherited-seat
Use when you have just been primed into an EXISTING seat through a planned handover — a different agent retired and handed you the seat plus its earned context — and you need a world model of what just happened to you. Covers how a handover differs from compaction and from a fresh launch, the…
claude-compaction-restore
Use when a Claude Code session has just compacted, is about to compact, reached context limit, resumed after /compact, or needs to rebuild its working mental model from Claude JSONL transcripts and touched files.
openrig-skills
Use when you're operating OpenRig and need the right skill or context for fleet recovery, seat handover, new-seat orientation, a watchdog wake, cross-host reach to an agent on another machine, rig packaging, an OpenRig upgrade, systematic debugging, queue triage, or implementation planning; also use when you don't…
seat-continuity-and-handover
Use when replacing a seat's occupant (rebuild/handover/swap), reasoning about stable-seat-identity vs fluid-occupant-identity, choosing an old-occupant disposition (retire/advise/shadow), or recording provenance for an occupant change. Two independent outcomes (continuityOutcome + seatBindingOutcome) and the 5 failure…