A guided workflow for pulling and shipping the next weekly GitHub ticket. It creates a pull request, coordinates automated reviews, fixes genuine issues, and merges the work when the ticket allows it.

Use it to take the next eligible AgentGuard ticket from selection through review, merge, and a summary of what shipped.

It removes the repeated manual steps of selecting the next ticket, checking project rules, getting reviews, and completing the change.

How bmdhodl/agent47 configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to bmdhodl/agent47. 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/bmdhodl/agent47/main/.agents/skills/next-ticket/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bmdhodl/agent47

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bmdhodl/agent47/next-ticket/github.svg)](https://agentmods.dev/skills/bmdhodl/agent47/next-ticket)

Your own site

<a href="https://agentmods.dev/skills/bmdhodl/agent47/next-ticket"><img src="https://agentmods.dev/badge/skills/bmdhodl/agent47/next-ticket/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/bmdhodl/agent47/next-ticket"><img src="https://agentmods.dev/badge/skills/bmdhodl/agent47/next-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 928 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00093	$0.00928
Opus 5.5	$0.00037	$0.00371
Sonnet 5.5	$0.00019	$0.00186
Haiku 4.5	$0.00009	$0.00093

Measured 1mo ago against content hash 167c1b91b2f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/check_links.py), 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.

.agents/skills/next-ticket/SKILL.md · 78 lines

How it starts

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

Next ticket

You are the lead senior engineer. Do this once, then stop. Do not start another ticket in the same turn.

The owner saying "next ticket" is the selection. The planning-only label does not block that.

1. Pull the next ticket

Planning authority is GitHub #729 and Project 4. ops/03-ROADMAP_NOW_NEXT_LATER.md is a view, not a second queue.

gh issue list --repo bmdhodl/agent47 --state open --label roadmap:2026-weekly --limit 50

Take the first open ticket in the newest ordered sequence table in #729 (for example "Adoption sequence updated September 24"). Only if #729 has no such table, take the lowest open AG- issue. Skip any ticket that #729, the ticket, or a linked issue marks held, conditional, or blocked on an unmet gate. Read that issue before coding.

If the next ticket's acceptance needs outside people (testers, posts, replies) that an agent cannot produce, ship only the repo-side slice the ticket names and tell the owner what is still theirs. Also read memory/, ops/00-NORTHSTAR.md, ops/03-ROADMAP_NOW_NEXT_LATER.md, ops/04-DEFINITION_OF_DONE.md, and ops/FOLLOWUP.md.

Stay inside the ticket. The SDK stays MIT and zero-dependency. No paid features, no dashboard work, no new public export, and no release tag unless the ticket says so.

2. Ship it

Work on a branch off main. Open the PR ready for review. Never open a draft.

Follow the repo's existing proof rules: tests, showwork claims, and a short PR body with the command output.

3. QA

Ask Bugbot and Copilot to review the open PR. Wait until each one has either a real review or an explicit skip.

A usage-limit, quota, or "couldn't run" comment is a skip, not a code defect. Do not reply to each repeat of that skip.

If both Bugbot and Copilot skipped, send the diff to a model other than the one that wrote the PR. Ask that model only for bugs, security problems, and broken behavior. Do not review your own diff with the same model.

Read the full file on GitHub · 78 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/check_links.py 826 B 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.

1mo ago Changed 167c1b91b2f3
1mo ago First seen · 78 lines · 93 tokens per session scan A 44c2204ec123

Subscribe to this mod's changes

next-ticket is a skill published in the GitHub repository bmdhodl/agent47 (4 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 928 once invoked, about $0.0004 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-09-26.

AI Safety Commits Git and workflow Guardrails LangChain Project management ai-agents anthropic developer-tools

next-ticket next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
next-ticketbmdhodl/agent47	Skill	4	2d ago	MIT	A	93	Claude Code, Codex
caveman-commitJuliusBrussee/caveman	Skill	118k	yesterday	Apache-2.0	A	38	Claude Code
gitasgeirtj/system_prompts_leaks	Skill	71k	2d ago	CC0-1.0	A	163	Claude Code
git-advanced-workflowswshobson/agents	Skill	42k	yesterday	MIT	A	54	Claude Code
llamaguarddavila7/claude-code-templates	Skill	33k	yesterday	MIT	A	74	Claude Code, Codex
changelogDonchitos/Claude-Code-Game-Studios	Skill	36k	18d ago	MIT	A	22	Claude Code
workflow-patternswshobson/agents	Skill	42k	yesterday	MIT	A	35	Claude Code

agent47: Skill for Claude Code