Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nth5693/gemini-kitnpx agentmods add skills/nth5693/gemini-kit/file-todosWrote 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/nth5693/gemini-kit/file-todos)<a href="https://agentmods.dev/skills/nth5693/gemini-kit/file-todos"><img src="https://agentmods.dev/badge/skills/nth5693/gemini-kit/file-todos.svg" alt="Measured on agentmods" 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.00014 | $0.00482 |
| Opus 5 | $0.00007 | $0.00241 |
| Sonnet 5 | $0.00003 | $0.00096 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
file-todos 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- file-todos — 100% identical, 0 lines differ
- file-todos — 100% identical, 0 lines differ
What it actually says
File-Based Todo Tracking
Provides workflows for creating, managing, and completing todos stored as markdown files.
Overview
The todos/ directory contains markdown files with YAML frontmatter for tracking work items.
File Naming Convention
{issue_id}-{status}-{priority}-{description}.md
Examples:
001-pending-p1-security-fix.md
002-ready-p2-performance-opt.md
003-complete-p3-cleanup.md
Status Lifecycle
pending → ready → complete
↓
(deleted if skipped)
What do you want to do?
- Create a todo → See "Creating Todos" below
- Triage pending items → Use
/triage - Work on todos → Use
/resolve_todo - Check dependencies → See "Dependency Management" below
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "file-todos" "manual" "$$"
Creating Todos
# Get next ID
next_id=$(ls todos/*.md 2>/dev/null | grep -o '[0-9]\+' | sort -n | tail -1 | awk '{printf "%03d", $1+1}')
[ -z "$next_id" ] && next_id="001"
# Copy template
cp todos/todo-template.md todos/${next_id}-pending-{priority}-{description}.md
Dependency Management
# In YAML frontmatter
dependencies: ["001", "002"] # Blocked by these issues
dependencies: [] # No blockers
Check blockers:
grep "dependencies:" todos/{file}.md
Quick Commands
# List by status
ls todos/*-pending-*.md
ls todos/*-ready-*.md
ls todos/*-complete-*.md
# List by priority
ls todos/*-p1-*.md
# Count by status
for s in pending ready complete; do
echo "$s: $(ls todos/*-$s-*.md 2>/dev/null | wc -l)"
done
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 · 14 tokens per session scan A 01f82ff356ae
file-todos is a skill published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 482 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-30.
Other skills, from other repositories
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
multica-goal-tracker
Track goal-driven Multica issues. Use when a user creates or maintains Multica issues by pasting a /goal prompt, wants Codex to summarize that goal into a concise issue purpose, append a normalized goal-start comment, record completion evidence from real Multica execution run messages or a supplied session transcript…
jira
Read and write Jira issues, comments, transitions via the Jira REST API v3.
todoist
Manage Todoist tasks and projects via the Todoist REST API v2.
trello
Manage Trello boards, lists, and cards via the Trello REST API.
jira-integration
Use this skill when retrieving Jira tickets, analyzing requirements, updating ticket status, adding comments, or transitioning issues. Provides Jira API patterns via MCP or direct REST calls.