Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/lossless-group/lossless-agent-skills/gh-cli-projects-tasks-conventions)<a href="https://agentmods.dev/skills/lossless-group/lossless-agent-skills/gh-cli-projects-tasks-conventions"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/gh-cli-projects-tasks-conventions/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/lossless-group/lossless-agent-skills/gh-cli-projects-tasks-conventions"><img src="https://agentmods.dev/badge/skills/lossless-group/lossless-agent-skills/gh-cli-projects-tasks-conventions.svg" alt="Reviewed on agentmods" width="80" 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.00316 | $0.05642 |
| Opus 5 | $0.00158 | $0.02821 |
| Sonnet 5 | $0.00063 | $0.01128 |
| Haiku 4.5 | $0.00032 | $0.00564 |
Grade A, and why
gh-cli-projects-tasks-conventions 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 10d 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
86% identical to 043-planning-github-issues — 395 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gh CLI · Projects & Tasks Conventions
Premature on purpose — 2026-06-05. We don't yet have many preferences. The ones that exist are codified here so they don't drift in the meantime — listed in order of priority to adhere to, not in the order they were added: (1) compose with [[pseudomonorepos]] to figure out which repo a local path actually lives in; (2) every task body that points at a
context-v/file points at it via a clickable GitHub URL; (3) pin the branch explicitly when worktrees are in play, becauseHEADanswers per-worktree; (4) prefill the issue sidebar — assignee, label, type, milestone — by querying the available options and inferring best fit, asking the user only when nothing fits (Convention 6). As more conventions emerge (status field discipline, priority discipline, custom-field schemas, project-per-app vs project-per-engagement), they get added here.
When to use this skill
- Creating, editing, or listing GitHub Project tasks via
gh project— particularlyitem-create,item-add,item-edit. - Creating repo issues via
gh issue createwhose sidebar (assignee, labels, type, milestone) should arrive prefilled (Convention 6). - The user says "create a task," "add to the project," "draft a project item," "set up a project," "gh project," or any variant.
- An agent is about to author a task body that references one or more
context-v/files anywhere in the pseudomonorepo tree. - Scripting bulk task creation from a spec, exploration, or plan that has sections / decisions / placeholders worth tracking.
- Any of the above while git worktrees are in play — multiple checkouts of the same repo at different branch tiers change what
HEADresolves to, and therefore which branch ends up in the link (Convention 3b).
Compose with pseudomonorepos
This skill assumes [[pseudomonorepos]] is in context. The tree-walking discipline there is what makes the link-building behavior below correct: a context-v/ file at /Users/mpstaton/code/lossless-monorepo/ai-labs/context-v/explorations/X.md does not live in the lossless-monorepo repo on GitHub — it lives in the ai-labs repo, which is submoduled. The link convention below depends on resolving the right repo before building the URL.
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.
- 10d ago First seen · 379 lines · 316 tokens per session scan A 743ae101924c
gh-cli-projects-tasks-conventions is a skill published in the GitHub repository lossless-group/lossless-agent-skills (4 stars, last pushed 17d ago), licensed MIT. It adds 316 tokens to every session and 5,642 once invoked, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to 043-planning-github-issues, differing in 395 lines, and is treated as a copy.
Other skills, from other repositories
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd-pause-work
Create context handoff when pausing work mid-phase.