agentmods.dev

github-todo-triage

github-todo-triage is a skill for Claude Code, Codex from xing5/mcp-google-sheets. It costs 73 tokens per session (1,046 once invoked), scanned A, original, MIT.

A repository workflow for fetching and organizing GitHub issues, pull requests, and project todos. It maintains a local status file and groups work by type and priority.

In plain words
What is it for?
Use it to inspect open issues and pull requests, check whether main already contains a fix, prioritize tasks, and update the local todo ledger.
Why use it?
It gives maintainers a repeatable way to refresh GitHub information and decide what needs attention without changing GitHub records.

Skill for Claude CodeCodex

not rated 996 +5 3mo ago A scan 73 tokens original MIT
View the source file xing5/mcp-google-sheets
Install

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.

agentmods
npx agentmods add skills/xing5/mcp-google-sheets/github-todo-triage
Any agent
npx skills add xing5/mcp-google-sheets --skill github-todo-triage
Clone the repo
git clone --depth 1 https://github.com/xing5/mcp-google-sheets

Made for: Claude Code, Codex.

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 github-todo-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/xing5/mcp-google-sheets/github-todo-triage.svg)](https://agentmods.dev/skills/xing5/mcp-google-sheets/github-todo-triage)
Your own site
<a href="https://agentmods.dev/skills/xing5/mcp-google-sheets/github-todo-triage"><img src="https://agentmods.dev/badge/skills/xing5/mcp-google-sheets/github-todo-triage.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,046 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00073 $0.01046
Opus 5 $0.00036 $0.00523
Sonnet 5 $0.00015 $0.00209
Haiku 4.5 $0.00007 $0.00105

Measured 5d ago against content hash a4a92f707201, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-todo-triage 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/fetch-todos.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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

Copies of this mod

3 near-identical copies found in the catalogue:

.codex/skills/github-todo-triage/SKILL.md · 82 lines

How it starts

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

GitHub Todo Triage

Use this workflow when the user asks to check GitHub issues, pull requests, project todos, maintainer status, or what to work on next.

State Files

  • Status ledger: TODO_STATUS.md
  • Raw GitHub snapshots: .codex/github-todos/
  • Fetch helper: .codex/skills/github-todo-triage/scripts/fetch-todos.sh

Workflow

  1. Confirm the repo and account.

    • Run git remote -v and gh auth status.
    • Prefer the active xing5 GitHub account when working on this repository.
    • Use gh repo view --json nameWithOwner -q .nameWithOwner or the origin remote to identify the GitHub repo.

  2. Refresh GitHub state.

    • Run .codex/skills/github-todo-triage/scripts/fetch-todos.sh.
    • If the script fails, run equivalent gh issue list and gh pr list commands manually.
    • Do not close, merge, label, assign, or comment on GitHub unless the user explicitly asks.

  3. Review open issues.

    • Group issues into: bugs/support, feature requests, docs/setup, ecosystem/registry, and stale or closeable.
    • Check whether main already implements the requested capability before treating an issue as active work.
    • For support issues, look for reproduction details, version, auth mode, transport, and client.

  4. Review open PRs.

    • Check mergeability, conflicts, review comments, changed files, and overlap with other PRs.
    • Prefer small clean bugfix PRs before large overlapping feature/refactor PRs.
    • Treat conflicting PRs as active only after rebasing or replacing them against current main.

  5. Enforce the test gate.

    • Do not implement or merge feature changes before defining the tests that prove the behavior.
    • Prefer unit tests with fake Google API services for request construction, argument handling, return shape, and error paths.
    • Use live Google integration tests only for behavior that cannot be validated with fakes, and keep them opt-in through environment variables.
    • For every PR, record whether tests are missing, unit-only, integration-ready, or verified live.

Read the full file on GitHub · 82 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 5d ago First seen · 82 lines · 73 tokens per session scan A a4a92f707201

Subscribe to this mod's changes

github-todo-triage is a skill published in the GitHub repository xing5/mcp-google-sheets (996 stars, last pushed 3mo ago), licensed MIT. It adds 73 tokens to every session and 1,046 once invoked, about $0.0004 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.

Git and workflowProject managementgooglemcpmcp-serverspreadsheet
Related

Other skills, from other repositories

guides

This guide helps Claude (and other AI assistants) use ServalSheets MCP server effectively.

khill1269/servalsheets · 18 tokens

google-sheets-expert

Enterprise-grade Google Sheets MCP server (ServalSheets) with tool categories and specialized actions. Implements UASEV+R protocol for intelligent spreadsheet operations with transaction support, AI analysis, conversational context, and MCP 2025-11-25 compliance.

khill1269/servalsheets · 56 tokens

ship

Run the full pre-commit verification pipeline and prepare a commit. Checks types, tests, drift, placeholders, and silent fallbacks before committing.

khill1269/servalsheets · 31 tokens

debug

Trace a ServalSheets failure through the 4-layer pipeline to find the exact origin. Use when tests fail unexpectedly, behavior doesn't match schema, or a specific error needs root cause analysis.

khill1269/servalsheets · 40 tokens

implement

Implement a ServalSheets feature or fix using the full research → implementation → validation → review pipeline.

khill1269/servalsheets · 22 tokens

review

Run a comprehensive multi-perspective code review on staged or recent changes. Covers TypeScript types, MCP compliance, Google API best practices, security, and test coverage.

khill1269/servalsheets · 35 tokens