yougile

yougile is a skill for Claude Code, Codex from nebelov/yougile-mcp. It costs 32 tokens per session (1,047 once invoked), scanned A, original, MIT.

A set of rules for managing tasks in YouGile, a project-management tool with boards, columns, stickers, and departments. It covers creating, updating, moving, searching, auditing, and completing tasks through its connection for coding agents.

In plain words
What is it for?
Use it to maintain YouGile task backlogs, check for duplicates, assign task categories, move work between columns, and attach results when closing tasks.
Why use it?
It reduces duplicate tasks and keeps completed work traceable by requiring links, summaries, and dates in task descriptions. It also provides project-specific settings for boards, columns, and task colors.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to maintain YouGile task backlogs, check for duplicates, assign task categories, move work between columns, and attach results when closing tasks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nebelov/yougile-mcp/skill
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.

Any agent
npx skills add nebelov/yougile-mcp --skill skill
Clone the repo
git clone --depth 1 https://github.com/nebelov/yougile-mcp

Made for: Claude Code, Codex.

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

agentmods badge for yougile

README.md
[![agentmods](https://agentmods.dev/badge/skills/nebelov/yougile-mcp/skill/github.svg)](https://agentmods.dev/skills/nebelov/yougile-mcp/skill)
Your own site
<a href="https://agentmods.dev/skills/nebelov/yougile-mcp/skill"><img src="https://agentmods.dev/badge/skills/nebelov/yougile-mcp/skill/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.

agentmods 80×15 button for yougile

Your own site · 80×15
<a href="https://agentmods.dev/skills/nebelov/yougile-mcp/skill"><img src="https://agentmods.dev/badge/skills/nebelov/yougile-mcp/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,047 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00032 $0.01047
Opus 5 $0.00016 $0.00524
Sonnet 5 $0.00006 $0.00209
Haiku 4.5 $0.00003 $0.00105

Measured 9d ago against content hash d00eb642fa30, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

yougile 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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • yougile — 100% identical, 0 lines differ
skill/SKILL.md · 141 lines

How it starts

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

YouGile MCP — Task Management Best Practices

When to use

  • Creating / updating / moving tasks in YouGile
  • Task inventory and audits
  • Searching tasks by assignee, sticker, or title
  • Managing boards, columns, stickers, departments

YOUR CONFIG

Customize these for your project:

PROJECT_ID: <your-project-uuid>
BOARD_IDS:
  - name: "Development"
    id: <board-uuid>
    columns:
      - Backlog: <column-uuid>
      - In Progress: <column-uuid>
      - Done: <column-uuid>

TASK_COLORS:
  - blue: Features
  - red: Bugs
  - yellow: Infrastructure
  - green: Marketing
  - violet: Product/UX

Rules

1. Always attach results when closing a task

NOT JUST: completed=true, columnId=Done
BUT:      completed=true, columnId=Done, description=<links to results>

Add to description:

  • Links to result files (docs, code, configs)
  • Brief summary of what was done
  • Completion date

2. Check for duplicates before creating

Before yougile_create_task ALWAYS:

  1. yougile_list_tasks(columnId=backlog) — check backlog
  2. yougile_list_tasks(title=keyword) — search by keyword
  3. If similar task exists — update it, don't create a new one

3. Verify task isn't already done

Before creating, check:

  • "Done" columns on relevant boards
  • Project docs and results files
  • Existing implementations in code

4. WIP limit

Keep "In Progress" column lean. Don't overload.

5. Task description format

<p>Brief description (1-2 sentences).</p>

<p><b>MATERIALS:</b></p>
<ul>
<li><b>Name:</b> /path/to/file.md</li>
</ul>

Always include links to relevant research/docs.

API Patterns (important!)

Deletion

  • Soft delete via PUT {deleted: true} — works for ALL entities
  • Hard DELETE — ONLY works for project roles (DELETE /projects/{id}/roles/{roleId})
  • Everything else returns 404 on DELETE method

Task assigned field

  • assigned is a UUID array: ["uuid1", "uuid2"]
  • NOT an object! Don't pass {uuid: true}

Chat messages

  • Endpoint: /chats/{chatId}/messages where chatId = taskId OR groupChatId
  • PUT messages supports ONLY {deleted: true}cannot edit message text
  • Sticker fields use name (NOT title)

Read the full file on GitHub · 141 lines

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. 9d ago First seen · 141 lines · 32 tokens per session scan A d00eb642fa30

Subscribe to this mod's changes

yougile is a skill published in the GitHub repository nebelov/yougile-mcp (9 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,047 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens