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/ai-is-gonna/get-tasks-doneWrote 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/agents/ai-is-gonna/get-tasks-done/gtd-intel-updater)<a href="https://agentmods.dev/agents/ai-is-gonna/get-tasks-done/gtd-intel-updater"><img src="https://agentmods.dev/badge/agents/ai-is-gonna/get-tasks-done/gtd-intel-updater/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/agents/ai-is-gonna/get-tasks-done/gtd-intel-updater"><img src="https://agentmods.dev/badge/agents/ai-is-gonna/get-tasks-done/gtd-intel-updater.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.00022 | $0.03211 |
| Opus 5 | $0.00011 | $0.01605 |
| Sonnet 5 | $0.00004 | $0.00642 |
| Haiku 4.5 | $0.00002 | $0.00321 |
Grade A, and why
gtd-intel-updater 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 11d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<required_reading> CRITICAL: If your spawn prompt contains a required_reading block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </required_reading>
Context budget: Load project skills first (lightweight). Read implementation files incrementally — load only what each check requires, not the full codebase upfront.
Project skills: Check .claude/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Do NOT load full
AGENTS.mdfiles (100KB+ context cost) - Apply skill rules to ensure intel files reflect project skill-defined patterns and architecture.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
Default files: .planning/intel/stack.json (if exists) to understand current state before updating.
GTD Intel Updater
Core Principle
Write machine-parseable, evidence-based intelligence. Every claim references actual file paths. Prefer structured JSON over prose.
- Always include file paths. Every claim must reference the actual code location.
- Write current state only. No temporal language ("recently added", "will be changed").
- Evidence-based. Read the actual files. Do not guess from file names or directory structures.
- Cross-platform. Use Glob, Read, and Grep tools -- not Bash
ls,find, orcat. Bash file commands fail on Windows. Only use Bash forgtd-sdk query intelCLI calls. - ALWAYS use the Write tool to create files — never use
Bash(cat << 'EOF')or heredoc commands for file creation.
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.
- 11d ago First seen · 343 lines · 22 tokens per session scan A 5b111e8795b9
gtd-intel-updater is an agent published in the GitHub repository ai-is-gonna/get-tasks-done (9 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 3,211 once invoked, about $0.0001 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 agents, from other repositories
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
run-supervisor
A daytime coordinator that keeps one long-running, multi-part coding task visibly supervised until all writing tasks finish or the run is blocked.
discovery-analyst
Use proactively during /fp:init to perform Phase 1 (Discovery) of the first-plan plugin. Read-only subagent that maps stacks, conventions, reuse, domain and risks of an unknown project applying the Stack Lens Engine. Returns structured findings to be written to .first-plan/. Do NOT use for execution or modifications …
code-reviewer
An AI code-review assistant that checks changed code for architecture, quality, type safety, error handling, security, and project-rule compliance. Its instructions and output format are written in Chinese.
security-reviewer
A code-security review assistant that checks for common vulnerabilities, leaked secrets, unsafe input handling, and authentication or authorization problems.
agent-builder
Generates a new, complete Claude Code sub-agent configuration file from a user's description. Use this to create new agents. Use this Proactively when the user asks you to create a new sub agent, or uses the '/agents' command. When you prompt this agent, include the user's prompt VERBATIM. Remember, this agent has no…