Borrowing it
Nothing to install: this file belongs to dhawalshah/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.
curl -O https://raw.githubusercontent.com/dhawalshah/mcp-google-sheets/main/.codex/skills/github-todo-triage/SKILL.mdgit clone --depth 1 https://github.com/dhawalshah/mcp-google-sheetsWrote 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/dhawalshah/mcp-google-sheets/github-todo-triage)<a href="https://agentmods.dev/skills/dhawalshah/mcp-google-sheets/github-todo-triage"><img src="https://agentmods.dev/badge/skills/dhawalshah/mcp-google-sheets/github-todo-triage.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.00073 | $0.01046 |
| Opus 5 | $0.00036 | $0.00523 |
| Sonnet 5 | $0.00015 | $0.00209 |
| Haiku 4.5 | $0.00007 | $0.00105 |
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 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.
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.
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 -vandgh auth status. - Prefer the active
xing5GitHub account when working on this repository. - Use
gh repo view --json nameWithOwner -q .nameWithOwneror theoriginremote to identify the GitHub repo.
- Run
-
Refresh GitHub state.
- Run
.codex/skills/github-todo-triage/scripts/fetch-todos.sh. - If the script fails, run equivalent
gh issue listandgh pr listcommands manually. - Do not close, merge, label, assign, or comment on GitHub unless the user explicitly asks.
- Run
-
Review open issues.
- Group issues into: bugs/support, feature requests, docs/setup, ecosystem/registry, and stale or closeable.
- Check whether
mainalready 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.
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.
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.
- 7d ago First seen · 82 lines · 73 tokens per session scan A a4a92f707201
github-todo-triage is a skill published in the GitHub repository dhawalshah/mcp-google-sheets (0 stars, last pushed 2mo 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. It is 100% identical to github-todo-triage, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.