git-project-xray-mcp: Command for Claude Code

.claude/commands/gsd/add-todo.md

gsd:add-todo is a command for Claude Code from Jamie-BitFlight/git-project-xray-mcp. It costs 16 tokens per session (1,308 once invoked), scanned A, a copy of gsd:add-todo, MIT.

A command for capturing an idea or task from the current conversation as a todo item.

In plain words
What is it for?
Use it to create a todo with a short title, problem, possible solution, related files, and an area such as testing, documentation, or planning.
Why use it?
It records useful work without interrupting the task already in progress or losing important context.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is Jamie-BitFlight/git-project-xray-mcp's own configuration. It tells Claude Code how to work on git-project-xray-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything git-project-xray-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Jamie-BitFlight/git-project-xray-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Jamie-BitFlight/git-project-xray-mcp/main/.claude/commands/gsd/add-todo.md
Clone the repo
git clone --depth 1 https://github.com/Jamie-BitFlight/git-project-xray-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for gsd:add-todo

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/add-todo.svg)](https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/add-todo)
Your own site
<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/add-todo"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/add-todo.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.01308
Opus 5 $0.00008 $0.00654
Sonnet 5 $0.00003 $0.00262
Haiku 4.5 $0.00002 $0.00131

Measured 7d ago against content hash 0d0f29f068ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gsd:add-todo 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 7d 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.

Origin

This is a copy

98% identical to gsd:add-todo — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/gsd/add-todo.md · 194 lines

How it starts

The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Enables "thought → capture → continue" flow without losing context or derailing current work.

Note existing areas for consistency in infer_area step.

Without arguments: Analyze recent conversation to extract:

  • The specific problem, idea, or task discussed
  • Relevant file paths mentioned
  • Technical details (error messages, line numbers, constraints)

Formulate:

  • title: 3-10 word descriptive title (action verb preferred)
  • problem: What's wrong or why this is needed
  • solution: Approach hints or "TBD" if just an idea
  • files: Relevant paths with line numbers from conversation
Path pattern Area
src/api/*, api/* api
src/components/*, src/ui/* ui
src/auth/*, auth/* auth
src/db/*, database/* database
tests/*, __tests__/* testing
docs/* docs
.planning/* planning
scripts/*, bin/* tooling
No files or unclear general

Use existing area from step 2 if similar match exists.

If potential duplicate found:

  1. Read the existing todo
  2. Compare scope

If overlapping, use AskUserQuestion:

  • header: "Duplicate?"
  • question: "Similar todo exists: [title]. What would you like to do?"
  • options:
    • "Skip" — keep existing todo
    • "Replace" — update existing with new context
    • "Add anyway" — create as separate todo

Generate slug from title (lowercase, hyphens, no special chars in FILENAME only).

Write to .planning/todos/pending/${date_prefix}-${slug}.md:

---
created: [timestamp]
title: [title]
area: [area]
files:
  - [file:lines]
---

## Problem

[problem description - enough context for future Claude to understand weeks later]

## Solution

[approach hints or "TBD"]
  1. Count todos: ls .planning/todos/pending/*.md 2>/dev/null | wc -l
  2. Update "### Pending Todos" under "## Accumulated Context"

Check planning config:

COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false

If COMMIT_PLANNING_DOCS=false: Skip git operations, log "Todo saved (not committed - commit_docs: false)"

If COMMIT_PLANNING_DOCS=true (default):

git add .planning/todos/pending/[filename]
[ -f .planning/STATE.md ] && git add .planning/STATE.md
git commit -m "$(cat <<'EOF'
docs: capture todo - [title]

Area: [area]
EOF
)"

Confirm: "Committed: docs: capture todo - [title]"

[title] Area: [area] Files: [count] referenced


Would you like to:

  1. Continue with current work
  2. Add another todo
  3. View all todos (/gsd:check-todos)
</step>

</process>

<output>
- `.planning/todos/pending/[date]-[slug].md`
- Updated `.planning/STATE.md` (if exists)
</output>

<anti_patterns>
- Don't create todos for work in current plan (that's deviation rule territory)
- Don't create elaborate solution sections — captures ideas, not plans
- Don't block on missing information — "TBD" is fine
</anti_patterns>

Read the full file on GitHub · 194 lines

Changes

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.

  1. 7d ago First seen · 194 lines · 16 tokens per session scan A 0d0f29f068ba

Subscribe to this mod's changes

gsd:add-todo is a command published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 1,308 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to gsd:add-todo, differing in 2 lines, and is treated as a copy.