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 timurgaleev/memex --skill daily-task-managergit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/daily-task-manager)<a href="https://agentmods.dev/skills/timurgaleev/memex/daily-task-manager"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/daily-task-manager/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/timurgaleev/memex/daily-task-manager"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/daily-task-manager.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.00031 | $0.00486 |
| Opus 5.5 | $0.00012 | $0.00194 |
| Sonnet 5.5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
daily-task-manager 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 1mo 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
Daily Task Manager
Contract
This skill guarantees:
- Tasks stored as a brain page (
tasks/tasks.md) with structured format - Task lifecycle: add → in-progress → complete | defer
- Priority levels: P0 (urgent), P1 (today), P2 (this week), P3 (backlog)
- Completed tasks archived with completion date
- Deferred tasks carry forward with reason
Phases
- Load current tasks.
page_get tasks/tasks— read the task list. - Execute the requested action:
- Add: Append task with priority, description, due date. Record it with
add_timeline_event. - Complete: Mark as done, move to completed section with date.
- Defer: Move to next day/week with reason.
- Remove: Delete from list (rare, prefer complete or defer).
- Review: Display all active tasks by priority.
- Add: Append task with priority, description, due date. Record it with
- Save.
page_put tasks/tasks— write updated task list.
Output Format
# Tasks
## P0 — Urgent
- [ ] {task description} (due: {date})
## P1 — Today
- [ ] {task description}
## P2 — This Week
- [ ] {task description}
## P3 — Backlog
- [ ] {task description}
## Completed
- [x] {task} (completed: {date})
Anti-Patterns
- Adding tasks without a priority level
- Completing tasks without recording the completion date
- Deferring tasks without a reason
- Letting the task list grow unbounded (review weekly)
- Storing tasks outside the brain (they should be searchable)
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.
- 1mo ago First seen · 74 lines · 31 tokens per session scan A 9e4d92f93e3d
daily-task-manager is a skill published in the GitHub repository timurgaleev/memex (11 stars, last pushed 21d ago), licensed MIT. It adds 31 tokens to every session and 486 once invoked, about $0.0001 per session on Opus 5.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
swarm-mcp
Coordinate authorized work with local swarm peers through the available Swarm MCP interface, including durable messages, task ownership and handoffs.
report-issue-framework
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
trelly
Operate the trelly Trello CLI (npm trelly; bin trelly): auth setup/login, human vs --json output, boards/lists/cards, search, attachments, GitHub PR/commit links on cards, trelly ui, trelly api. Use when the user asks to run trelly commands, list or show Trello cards/todos, link a GitHub PR or commit to a card, or…
trelly-mcp
Configure and use the trelly MCP stdio server (trelloboardslist, trellocardcreate, trellosearch, trelloapiget, etc.). Use when wiring Cursor/Claude MCP, listing or showing Trello cards/todos, linking GitHub PRs/commits, or choosing MCP vs CLI.
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
issue-ingest
Full execution protocol for MODE: ISSUEINGEST -- GitHub issue intake, localization, spec generation, and transition to the full fix workflow.