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 linhai0872/dida365-agent --skill dida365git clone --depth 1 https://github.com/linhai0872/dida365-agentWrote 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/linhai0872/dida365-agent/dida365)<a href="https://agentmods.dev/skills/linhai0872/dida365-agent/dida365"><img src="https://agentmods.dev/badge/skills/linhai0872/dida365-agent/dida365/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/linhai0872/dida365-agent/dida365"><img src="https://agentmods.dev/badge/skills/linhai0872/dida365-agent/dida365.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.00244 | $0.01378 |
| Opus 5.5 | $0.00098 | $0.00551 |
| Sonnet 5.5 | $0.00049 | $0.00276 |
| Haiku 4.5 | $0.00024 | $0.00138 |
Grade A, and why
dida365 scanned grade A 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- 只用 `dida` 命令操作,禁止直接 curl / HTTP API / 浏览器。 How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
滴答清单 / TickTick (dida CLI)
通过 dida 命令操作滴答清单。所有命令默认输出 JSON 到 stdout;出错时信息进 stderr 且退出码非零。
本文件只讲何时用哪个命令、如何编排与决策;每个命令的字面参数请用 dida <group> <action> --help 查看。
严格遵守 (NEVER DO)
- 只用
dida命令操作,禁止直接 curl / HTTP API / 浏览器。 - 不要凭空编造 project_id / task_id —— 一律先用 list 命令拿到真实 ID。
- 删除类操作(
task delete/project delete/tag delete/folder delete)不可撤销,执行前先向用户确认。
前置约定
- 先拿 ID:任何针对具体任务/清单的操作前,先
dida project list拿 project_id;清单内任务用dida project data <projectId>或dida task filter。 - 任务的增删改查都需要 project_id 和 task_id(
get-by-id例外,只需 task_id)。 - 日期格式:
yyyy-MM-dd'T'HH:mm:ssZ,中国区用+0800。例:2026-05-29T15:00:00+0800。 - 优先级:0=无, 1=低, 3=中, 5=高。
- 状态:0=正常/未完成, 2=已完成。
- 习惯打卡日期用
YYYYMMDD(如20260529),与任务日期格式不同。
编排规则(多命令组合)
- "整理 / 复盘 / 我有哪些待办":先
dida task undone或dida task filter --status 0拉取,把结果呈现给用户确认,再执行后续移动/完成/删除。不要直接批量改。 - "本周/上周完成了什么":用
dida task completed --start-date ... --end-date ...。 - 创建任务但用户没指定清单:先
dida project list列出清单让用户选;不要随意猜一个 project_id。 - 批量操作优先用 batch 命令:要完成/创建/更新多条任务时,用
task batch-create/task batch-update/task batch-complete,而不是循环调用单条命令(更快、更省往返)。batch 命令通过--json '<JSON数组>'或--file <path>传入。
filter vs search 怎么选
dida task filter(V1):按结构化条件(清单、日期范围、优先级、标签、状态)筛选,标签是 AND 逻辑。无需 V2 配置。dida search <关键词>(V2):服务端全文搜索任务标题/内容。需要关键词匹配时用它,需要 V2 配置。
V2 能力(标签 / 搜索 / 父子任务 / 习惯 / 文件夹)
这些命令需要 V2 配置(DIDA365_V2_SESSION_TOKEN,或 DIDA365_USERNAME+DIDA365_PASSWORD)。
若命令报 "V2 not configured",告诉用户在 .env 里配置其一:
- 推荐:浏览器登录 dida365.com → F12 → Application → Cookies → 复制
t的值 → 设为DIDA365_V2_SESSION_TOKEN(约 30 天有效)。
错误恢复
- V1 401 / "Unauthorized":token 过期(约 180 天),运行
dida auth login重新授权;查看状态用dida auth status。 - V2 401:session token 过期(约 30 天),按上面 V2 说明更新
DIDA365_V2_SESSION_TOKEN。 - 404:project_id 或 task_id 不存在,用对应 list 命令重新获取有效 ID。
- 429:限流,等 30-60 秒再试。
命令速查(用 --help 看细节)
dida auth login | status | logout | token <TOKEN>dida project list | get | data | create | update | deletedida task create | update | get | get-by-id | complete | delete | move | completed | filter | undone | batch-create | batch-update | batch-complete | set-parent | unset-parent | pindida search <关键词>(V2)dida tag list | create | update | delete-batch | delete(V2)dida habit list | create | update | delete | checkin | undo-checkin | checkins | sections(V2)dida folder list | create | update | delete(V2)
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.
- 2mo ago First seen · 53 lines · 244 tokens per session scan A 90c5791ad6c0
dida365 is a skill published in the GitHub repository linhai0872/dida365-agent (2 stars, last pushed 5mo ago), licensed MIT. It adds 244 tokens to every session and 1,378 once invoked, about $0.0010 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
OpenSourceManagement
Triages open issues, pull requests and GitHub Discussions across the principal's own open-source repos (the list in Config.md) via the gh CLI, ranks what needs attention with suggested replies, posts edit-in-place marker comments, diffs new Ollama library models against a local model box, and takes a private repo…
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
cs-escalation-brief
Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…