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 charlie947/life-automation-skills --skill task-capturegit clone --depth 1 https://github.com/charlie947/life-automation-skillsWrote 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/charlie947/life-automation-skills/task-capture)<a href="https://agentmods.dev/skills/charlie947/life-automation-skills/task-capture"><img src="https://agentmods.dev/badge/skills/charlie947/life-automation-skills/task-capture/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/charlie947/life-automation-skills/task-capture"><img src="https://agentmods.dev/badge/skills/charlie947/life-automation-skills/task-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00140 | $0.01909 |
| Opus 5 | $0.00070 | $0.00955 |
| Sonnet 5 | $0.00028 | $0.00382 |
| Haiku 4.5 | $0.00014 | $0.00191 |
Grade A, and why
task-capture 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use this skill
Use it when the user wants their commitments pulled out of the noise and put somewhere they will actually see them:
- "Capture my tasks" / "extract my action items" / "what are my tasks from this?"
- "Turn this thread into to-dos" / "add this to my list"
- "Pull the action items out of this Slack channel / this email"
- The user pastes a message, thread, or transcript and wants the real jobs separated from the chatter.
- Any request to read across email or chat and produce a clean, filed task list.
Do not use it to decide priorities for the user, to invent deadlines that were never stated, or to write tasks to a list without showing them first. It captures and files. It does not do the work in the tasks.
What it needs (setup)
Two sides: a source to read, and a destination to write.
Read (pick either or both):
- Gmail connector: search and read threads. Read-only for this job. Claude never sends or drafts email here.
- Slack connector: read a channel, read a thread, search messages. Read-only. It sees only channels the user is a member of, and only messages Slack returns for the given scope.
Write, your task system (pick one):
- Notion connector: create pages in a tasks database. Needs the target database (or its URL) named up front.
- Airtable connector: create records in a table. Needs the base and table named up front.
- ClickUp, Asana, or Todoist: create tasks in your list, project, or board. Point the skill at the exact list or project to write into.
If a source is not connected, say which one and stop. Never fabricate the contents of an inbox or channel. If no destination is connected, still produce the task list in chat as a one-task-per-line block the user can paste anywhere.
The honest limit: there is no ambient capture. No connector lets Claude watch your inbox or Slack in the background. This skill is a pull, run when you ask. It captures from the exact scope you hand it in one session: a thread, a channel, a search window, or pasted text. It will not "keep an eye out" for future tasks, and it has no memory of what it captured last time. That is why dedupe reads the destination list live (see below) rather than trusting recall.
What ships with it
1 file 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.
- 12d ago First seen · 94 lines · 0 tokens per session scan A 1d6c708777b0
task-capture is a skill published in the GitHub repository charlie947/life-automation-skills (23 stars, last pushed 14d ago), licensed MIT. It adds 140 tokens to every session and 1,909 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.