agentmods.dev

fde

A general-purpose connection to the ClickUp API, the interface that lets software read and change ClickUp data. It supports custom requests when a more specific task operation is not available.

In plain words
What is it for?
Use it to make custom GET, POST, PUT, or DELETE requests for ClickUp tasks, documents, chat, attachments, time tracking, task moves, or audit logs.
Why use it?
It removes the need to build separate request code for each ClickUp endpoint. It also lets you work with both ClickUp API version 2 and version 3 where supported.

Skill for Claude CodeCodex

213 3d ago A scan 125 tokens original MIT
View the source file suboss87/FDEOps
Install

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.

agentmods
npx agentmods add skills/suboss87/fdeops/fde
Any agent
npx skills add suboss87/FDEOps --skill fde
Clone the repo
git clone --depth 1 https://github.com/suboss87/FDEOps

Made for: Claude Code, Codex.

Per session 125 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,573 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00125 $0.03573
Opus 5 $0.00063 $0.01786
Sonnet 5 $0.00025 $0.00715
Haiku 4.5 $0.00013 $0.00357

Measured 2d ago against content hash 88847ba3ec17, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fde 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.

skills/fde/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

@fde

Purpose

The engagement record for one client, from first meeting to signed outcome. One skill; six stages (land → close). Same map at any scale, on greenfield or brownfield, in any industry (overlays). You route; they never pick a skill. Confirm, then write .fde/. The workspace still compiles and commits. @fde does not leave.

When to use

  • They named a client, pasted notes, or asked what was agreed
  • The brief feels wrong, a sponsor went quiet, or Friday needs the ledger
  • Unbound - ask the name once, then you run fde resume --init

When NOT to use

A one-line typo or compile error in a file that will not ship. On a bound client: stay here for POC, characterisation, the change on their repo, eval, go-live, rollback, and acceptance.

Use these first

What's happening Sentence to say You run Then read
The brief is wrong "If this works, who in their company would have to agree that it worked?" fde resume then discover references/discover.md
They went quiet "Is this a process gap, or a trust problem?" fde log contact "…" --signal amber|red|green references/rescue.md
When did we agree? Don't argue from memory. Search the record. fde receipts <term> -
What's the outcome? A number nobody signed is claimed, not delivered. fde status references/readout.md

After a meeting: fde debrief --smart → confirm → --apply. Walk-in: fde prep. Friday: fde status.

Ground loop

On someone else's site the work is not "write code, remember later." Every change on a bound client stays on @fde:

  1. Name it in decisions.md (plan) or kill it in a day (poc).
  2. Characterise their code before you change it. Brownfield: their tests, their runner. Greenfield: the empty tree, first path they can click.
  3. Prove it on their staging. Staging they operate, a screen the signer in success.md can reject.
  4. If a model judges: evals.md Verdict SHIP before that change is done (eval-pack).
  5. Log delivery. Outcome is promised → measured → accepted, not a green CI. Then go live with a rollback you have run (ship).

Read the full file on GitHub · 207 lines

Files

What ships with it

36 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.

Changes

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.

  1. 2d ago First seen · 207 lines · 125 tokens per session scan A 88847ba3ec17

Subscribe to this mod's changes

fde is a skill published in the GitHub repository suboss87/FDEOps (213 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 3,573 once invoked, about $0.0006 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-30.

Project managementai-agentsclaude-skillscodex-skillcursorfdeforward-deployed-engineering
Related

Other skills, from other repositories

ulw-execute

Execute a Prometheus work plan with Boulder state, evidence ledger updates, worktree discipline, parallel subagents, and Stop-hook continuation. Use after planning when the user says ulw-execute, execute plan, continue plan, resume plan, or asks to run a .omo/plans plan.

code-yeongyu/oh-my-openagent · 64 tokens

prismer-im-collab

Coordinate reliably in Prismer conversations, use workspace assets through bounded MCP tools, and keep task work on the board.

Prismer-AI/PrismerCloud · 30 tokens

create-user-story

Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira).

huytieu/COG-second-brain · 23 tokens

retro

CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.

huytieu/COG-second-brain · 45 tokens

update-knowledge-base

Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync.

huytieu/COG-second-brain · 23 tokens

team

Invite humans into a workspace, propose collaborators for a project, and inspect the current human team. Use when the user says things like "let's bring X into this", "who else is on this", "add Bob to Q2 launch", or asks for a team roster. NEVER mints invites silently — the human must press a button.

Prismer-AI/PrismerCloud · 71 tokens