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 OPPO-Mente-Lab/X-OmniClaw --skill feishu-taskgit clone --depth 1 https://github.com/OPPO-Mente-Lab/X-OmniClawWrote 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/oppo-mente-lab/x-omniclaw/feishu-task)<a href="https://agentmods.dev/skills/oppo-mente-lab/x-omniclaw/feishu-task"><img src="https://agentmods.dev/badge/skills/oppo-mente-lab/x-omniclaw/feishu-task/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.
<a href="https://agentmods.dev/skills/oppo-mente-lab/x-omniclaw/feishu-task"><img src="https://agentmods.dev/badge/skills/oppo-mente-lab/x-omniclaw/feishu-task.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00539 |
| Opus 5 | $0.00010 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
feishu-task 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 12d 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
Feishu Task Tool
Tool feishu_task for task management operations.
Actions
List Tasks
{ "action": "list", "page_size": 20 }
Returns: user's tasks with details.
Get Task Details
{ "action": "get", "task_id": "task_xxx" }
Returns: complete task information including title, description, status, assignee, due date.
Create Task
{
"action": "create",
"title": "New Task",
"description": "Task description",
"due_date": "2024-12-31",
"assignee_id": "ou_xxx"
}
Creates a new task.
Update Task
{
"action": "update",
"task_id": "task_xxx",
"title": "Updated Title",
"status": "completed"
}
Updates an existing task.
Task Status
| Status | Description |
|---|---|
todo |
Not started |
in_progress |
In progress |
completed |
Completed |
canceled |
Canceled |
X-OmniClaw Implementation
Tool Class: FeishuTaskTools.kt
Available Tools:
feishu_task_list- List tasksfeishu_task_get- Get task detailsfeishu_task_create- Create taskfeishu_task_update- Update task
Example Usage:
// List tasks
val result = feishuTaskTools.listTasks(pageSize = 20)
// Create task
val result = feishuTaskTools.createTask(
title = "New Task",
description = "Description",
dueDate = "2024-12-31",
assigneeId = "ou_xxx"
)
// Update task status
val result = feishuTaskTools.updateTask(
taskId = "task_xxx",
status = "completed"
)
Use Cases
- Task Management: Create, update, list tasks
- Project Tracking: Track task status and progress
- Team Collaboration: Assign tasks to team members
- Reminders: Set due dates and reminders
Permissions
Required: task:task, task:task:readonly
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.
- 12d ago First seen · 105 lines · 21 tokens per session scan A 38c3047289fa
feishu-task is a skill published in the GitHub repository OPPO-Mente-Lab/X-OmniClaw (261 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 539 once invoked, about $0.0001 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.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
meta-meeting-to-workflow
Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
secretary
Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.