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.
git clone --depth 1 https://github.com/mikonos/LLM-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/commands/mikonos/llm-gtd/gtd-capture)<a href="https://agentmods.dev/commands/mikonos/llm-gtd/gtd-capture"><img src="https://agentmods.dev/badge/commands/mikonos/llm-gtd/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/commands/mikonos/llm-gtd/gtd-capture"><img src="https://agentmods.dev/badge/commands/mikonos/llm-gtd/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.00045 | $0.00402 |
| Opus 5 | $0.00023 | $0.00201 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
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 10d 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
<execution_context> @VAULT/.cursor/skills/gtd-harness/SKILL.md @VAULT/.cursor/skills/gtd-harness/capture/SKILL.md </execution_context>
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.
- 10d ago First seen · 32 lines · 45 tokens per session scan A 9f66cc0bedbc
gtd-capture is a command published in the GitHub repository mikonos/LLM-GTD (10 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 402 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-08-31.
Other commands, from other repositories
implement
Execute tasks from a track's implementation plan following TDD workflow.
new-track
Create a new track with specification and phased implementation plan.
status
Display project status, active tracks, and next actions.
team-delegate
Task delegation dashboard for managing team workload, assignments, and rebalancing.
team-status
Display team members, task status, and progress for an active agent team.
obsidian-board
Show or update a kanban board - flags overdue items, updates from conversation.