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 cynthiajones34/GBrain --skill daily-task-managergit clone --depth 1 https://github.com/cynthiajones34/GBrainWrote 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/cynthiajones34/gbrain/daily-task-manager)<a href="https://agentmods.dev/skills/cynthiajones34/gbrain/daily-task-manager"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/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/cynthiajones34/gbrain/daily-task-manager"><img src="https://agentmods.dev/badge/skills/cynthiajones34/gbrain/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.00471 |
| Opus 5 | $0.00015 | $0.00235 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 8d 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.
This is a copy
100% identical to daily-task-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Daily Task Manager
Contract
This skill guarantees:
- Tasks stored as a brain page (
ops/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.
gbrain get ops/tasks— read the task list. - Execute the requested action:
- Add: Append task with priority, description, due date. Add timeline entry.
- 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.
- Save.
gbrain put ops/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.
- 8d ago First seen · 71 lines · 31 tokens per session scan A e616f74a6bef
daily-task-manager is a skill published in the GitHub repository cynthiajones34/GBrain (0 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 471 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to daily-task-manager, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
create-user-story
Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira).
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
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.
team-brief
Generate daily team intelligence brief by cross-referencing GitHub, Linear, Slack, PostHog, meetings, and braindumps with two-way Linear sync-back.
update-knowledge-base
Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync.
gh-issues
Triage GitHub issues, select safe candidates, implement focused fixes, open pull requests, and address actionable review feedback.