Borrowing it
Nothing to install: this file belongs to rome-os/rome. 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/rome-os/rome/main/.claude/skills/todos-to-github-project/SKILL.mdgit clone --depth 1 https://github.com/rome-os/romeWrote 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/rome-os/rome/todos-to-github-project)<a href="https://agentmods.dev/skills/rome-os/rome/todos-to-github-project"><img src="https://agentmods.dev/badge/skills/rome-os/rome/todos-to-github-project/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.
<a href="https://agentmods.dev/skills/rome-os/rome/todos-to-github-project"><img src="https://agentmods.dev/badge/skills/rome-os/rome/todos-to-github-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00984 |
| Opus 5.5 | $0.00012 | $0.00394 |
| Sonnet 5.5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
todos-to-github-project 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todos to GitHub project
Goal end-state: every remaining todo of the conversation is one task-spec issue, the issues sit in one GitHub project, every dependency is a blocked-by edge on GitHub, and each in-scope issue carries ready-for-agent.
The issue format — title, body sections, the ready-for-agent bar — is defined in docs/authoring/github-issues.md and docs/authoring/github-issues-task-spec.md. Prose in titles and bodies follows docs/authoring/WRITING.md. This skill covers what to file, in which order, and with which gh calls.
1. Harvest
- Collect every remaining todo from the conversation: open task-list items, deferred follow-ups, and work the user parked for later.
- Search the tracker for each todo with
gh issue list --search "<keywords>". If an existing issue already tracks it, drop the todo from the set. - Write one sentence per todo stating the outcome its issue must deliver. If the sentence only makes sense with the conversation open, ask the user what the todo means.
2. Draft
- Name the project after the outcome the set delivers, not after the conversation.
- Split the todos into in-scope and out-of-scope. An out-of-scope todo files under its issue type with the type label, stays out of the project, and never carries
ready-for-agent. - Draft each in-scope issue as a task spec in the github-issues-task-spec.md format, title included.
- Wire the dependencies. Issue X is blocked by issue Y when X cannot start before Y merges. Record each edge as a Blocked by line in X's body.
- Check the edge graph for cycles. A cycle is a decomposition error — re-split the todos until the graph is acyclic.
- Apply the label bar from github-issues-task-spec.md: every in-scope issue gets
task, and an issue implementable from its body alone also getsready-for-agent. An issue still waiting on a user decision files withoutready-for-agent.
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.
- 1mo ago Changed beb1d069794a
- 1mo ago First seen · 53 lines · 30 tokens per session scan A 59b31c724084
todos-to-github-project is a skill published in the GitHub repository rome-os/rome (871 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 984 once invoked, about $0.0001 per session on Opus 5.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
pm-assistant
Product operations assistant strategy contract. PM short answers and deep analysis should be evidence-grounded and should separate facts from hypotheses. Model calls, hooks, queueing, cancellation, notifications, and staged task execution stay in Rust.
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.
company-hr
Run HR for a PenguinHarness organization — guarantee every employee has an enabled calendar event, hire and offboard employees (channels included), evaluate and improve them (with the default-rsi-toolkit plugin's agent-optimization skill), and keep the handbook's role conventions current.