What is github-todo-triage?

A repository workflow for fetching, reviewing, prioritizing, and recording todos from GitHub issues and pull requests. GitHub is a service where teams host code and track this work.

Use it to refresh GitHub state, group open work, check whether issues are already fixed, and update the local status record.

It keeps GitHub activity and the repository's todo ledger aligned while preventing unrequested changes to issues or pull requests.

How bankableco/mcp-google-sheets configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to bankableco/mcp-google-sheets. 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/bankableco/mcp-google-sheets/main/.codex/skills/github-todo-triage/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bankableco/mcp-google-sheets

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bankableco/mcp-google-sheets/github-todo-triage/github.svg)](https://agentmods.dev/skills/bankableco/mcp-google-sheets/github-todo-triage)

Your own site

<a href="https://agentmods.dev/skills/bankableco/mcp-google-sheets/github-todo-triage"><img src="https://agentmods.dev/badge/skills/bankableco/mcp-google-sheets/github-todo-triage/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bankableco/mcp-google-sheets/github-todo-triage"><img src="https://agentmods.dev/badge/skills/bankableco/mcp-google-sheets/github-todo-triage.svg" alt="Reviewed on agentmods" width="80" 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. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00073	$0.01046
Opus 5.5	$0.00029	$0.00418
Sonnet 5.5	$0.00015	$0.00209
Haiku 4.5	$0.00007	$0.00105

Measured 2mo ago against content hash a4a92f707201, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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

This is a copy

100% identical to github-todo-triage — 0 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.

.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

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

scripts/fetch-todos.sh 2.0 KB runs code

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.

2mo 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 bankableco/mcp-google-sheets (0 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,046 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github-todo-triage, differing in 0 lines, and is treated as a copy.

Git and workflow Project management

github-todo-triage next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
github-todo-triagebankableco/mcp-google-sheets	Skill	0	4mo ago	MIT	A	73	Codex
merge-batchdiegosouzapw/OmniRoute	Skill	83k	5d ago	MIT	A	46	Claude Code
prowler-commitprowler-cloud/prowler	Skill	15k	yesterday	Apache-2.0	A	44	Claude Code, Codex
gh-auth-isolationgithub/gh-aw	Skill	5.6k	yesterday	MIT	A	20	Claude Code, Codex
github-skillzeenie-ai/OpenCompany	Skill	1.1k	yesterday	MIT	A	51	Claude Code
comet-githubrpamis/comet	Skill	3.3k	yesterday	MIT	A	72	Claude Code, Codex
release-helperSahir619/fable-method	Skill	2.3k	1mo ago	MIT	A	43	Claude Code

mcp-google-sheets: Skill for Codex