Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add MadAppGang/magus/plugin install gtdWrote 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/madappgang/magus/gtd-capture)<a href="https://agentmods.dev/skills/madappgang/magus/gtd-capture"><img src="https://agentmods.dev/badge/skills/madappgang/magus/gtd-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/madappgang/magus/gtd-capture"><img src="https://agentmods.dev/badge/skills/madappgang/magus/gtd-capture.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.00037 | $0.00938 |
| Opus 5 | $0.00018 | $0.00469 |
| Sonnet 5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
gtd-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 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTD Capture Skill — Proactive Capture Trigger Detection
When This Skill Applies
Apply this skill whenever you detect any of the following semantic signals in the user's messages or code:
Explicit Capture Signals (→ Inbox)
- "I need to ___", "we need to ___", "you need to ___"
- "we should ___", "I should ___", "we ought to ___"
- "remind me to ___", "don't forget ___", "remember to ___"
- "TODO:", "FIXME:", "HACK:", "NOTE: action required"
- "must ___", "have to ___", "got to ___"
Waiting For Signals (→ Waiting list)
- "waiting on ___", "waiting for ___", "blocked by ___"
- "once ___ is done", "after ___ finishes", "depends on ___"
- "need ___ to respond", "need ___ from ___"
Deferral Signals (→ Someday/Maybe)
- "someday", "eventually", "later", "at some point"
- "when we have time", "would be nice to", "might want to"
- "tech debt", "backlog item", "refactor (not now)"
- "future improvement", "nice to have"
Frequency Guard
Maximum 2 capture suggestions per session. After 2 suggestions, stop offering — do not suggest a third time.
Track mentally whether you have already offered capture in this session.
How to Suggest
When you detect a capture signal, offer ONE of these phrasings (pick based on signal type):
Inbox capture:
Capture to GTD inbox? → "[detected text]" [y/N]
Waiting For capture:
Add to Waiting For: "[detected text]"? [y/N]
Someday/Maybe capture:
Add to Someday/Maybe: "[detected text]"? [y/N]
Response to User's Answer
If user says "y" or "yes": Run the Bash command to append to tasks.json:
CWD=$(pwd)
GTD_LIB="${CLAUDE_PLUGIN_ROOT}/hooks/gtd-lib.sh"
source "$GTD_LIB"
gtd_init
ID=$(gtd_new_id)
NOW=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
TASK_JSON=$(jq -n --arg id "$ID" --arg subject "<detected text>" --arg list "<inbox|waiting|someday>" --arg created "$NOW" \
'{id: $id, subject: $subject, list: $list, context: [], parentId: null, energy: null, timeEstimate: null, waitingOn: null, dueDate: null, created: $created, modified: $created, completed: null, notes: ""}')
echo "$TASK_JSON" | gtd_append_task
bun run "${CLAUDE_PLUGIN_ROOT}/tools/gtd-display.ts" capture "$ID" "<detected text>" --list "<inbox|waiting|someday>"
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 · 89 lines · 37 tokens per session scan A 16925744c7ff
gtd-capture is a skill published in the GitHub repository MadAppGang/magus (9 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 938 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…