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 saubakirov/trace-first-starter --skill daily-taskgit clone --depth 1 https://github.com/saubakirov/trace-first-starterWrote 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/saubakirov/trace-first-starter/daily-task)<a href="https://agentmods.dev/skills/saubakirov/trace-first-starter/daily-task"><img src="https://agentmods.dev/badge/skills/saubakirov/trace-first-starter/daily-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/saubakirov/trace-first-starter/daily-task"><img src="https://agentmods.dev/badge/skills/saubakirov/trace-first-starter/daily-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.00030 | $0.01826 |
| Opus 5.5 | $0.00012 | $0.00730 |
| Sonnet 5.5 | $0.00006 | $0.00365 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
tfw-daily-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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TFW Daily Task
Mindset: Working backwards from the result the person needs. State Goal and Value; test them
against the receiving project's North Star and Values. Challenge a weak premise with concrete
reasons. Use consequential Questions and Saint-Exupéry judgment: remove work that protects no
purpose, evidence or boundary. Daily names this bounded route, not a cadence or risk rating.
Authority: One actual worker performs the work the human's clear bounded request authorizes. The human retains purpose, accountability and acceptance. This optional route is outside formal Full task work; it grants no Coordinator, Executor or Reviewer authority in an active formal task. Title, model, profile, prior task and apparent urgency grant no permission.
1. Inspect before action
Read the applicable project instructions, personal preferences when present, existing Daily rules and actual request source. Follow local identity and record rules. Record the actual human and worker/source; disclose missing identity without inventing a handle. A missing profile alone does not block work when the actual request and authority are established. Missing request source or legitimate authority blocks the dependent action.
Inspect the current object and its governing product/document sources before historical work. Make one bounded search using the object's path, name or intended result in relevant recent Daily records and current project knowledge. Read convincing matches only. Record inspected paths and commit, hash or observed state; an honest no-match is enough. Check older work's scope, currentness, source, producer and authority. Resolve material successor/conflict relations using the project's existing knowledge rules. History never overrides current product truth merely because it is related.
Before the first material product write, retain an observable checkpoint in the selected record: actual source, inspected rules/current object, prior-work lookup/result, Goal, Value, North Star fit, Boundaries and completion oracle. Do not retrospectively claim this gate ran. The checkpoint is a compact statement of observations and decisions, not private reasoning or a questionnaire.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · +7 lines 61e17248a3d4
- 18d ago Changed · +34 lines 9530696e820e
- 22d ago First seen · 96 lines · 30 tokens per session scan A a453819bcee3
tfw-daily-task is a skill published in the GitHub repository saubakirov/trace-first-starter (30 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 1,826 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-09-29.
Other skills, from other repositories
digest
NOTE: this skill requires connected chat / email / project-tracker / docs MCPs, which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Cross-tool rollup of what's pending, what shipped, and what's blocked across chat / email / project tracker /…
agent-user-tools
Agent skill for user-tools - invoke with $agent-user-tools.
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…