coograph: Command for Claude Code

.claude/commands/coograph-new-ticket.md

coograph-new-ticket is a command for Claude Code from paullukic/coograph. It costs 0 tokens per session (509 once invoked), scanned A, original, MIT.

A command for starting work on a new software ticket. It checks the project, investigates the relevant code, and prepares an OpenSpec proposal—a written description of a planned change—for approval.

In plain words
What is it for?
Use it to review a ticket's requirements, find affected code and risks, and create a proposal before implementation.
Why use it?
It reduces the risk of implementing a vague or conflicting change by checking project rules and existing work first.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code; mentions AGENTS.md.

This is paullukic/coograph's own configuration. It tells Claude Code how to work on coograph itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything coograph configures →

Reuse

Borrowing it

Nothing to install: this file belongs to paullukic/coograph. 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/paullukic/coograph/main/.claude/commands/coograph-new-ticket.md
Clone the repo
git clone --depth 1 https://github.com/paullukic/coograph

Made for: Claude Code.

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.

agentmods badge for coograph-new-ticket

README.md
[![agentmods](https://agentmods.dev/badge/commands/paullukic/coograph/coograph-new-ticket/github.svg)](https://agentmods.dev/commands/paullukic/coograph/coograph-new-ticket)
Your own site
<a href="https://agentmods.dev/commands/paullukic/coograph/coograph-new-ticket"><img src="https://agentmods.dev/badge/commands/paullukic/coograph/coograph-new-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.

agentmods 80×15 button for coograph-new-ticket

Your own site · 80×15
<a href="https://agentmods.dev/commands/paullukic/coograph/coograph-new-ticket"><img src="https://agentmods.dev/badge/commands/paullukic/coograph/coograph-new-ticket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 509 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00509
Opus 5.5 $0.00000 $0.00204
Sonnet 5.5 $0.00000 $0.00102
Haiku 4.5 $0.00000 $0.00051

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

Security

Grade A, and why

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

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.

.claude/commands/coograph-new-ticket.md · 42 lines

How it starts

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

Start work on a new ticket below. Run pre-flight checks, investigate the codebase, and flow into an OpenSpec proposal.

The full procedure lives in .github/skills/coograph-new-ticket/SKILL.md. Follow those steps exactly, with these Claude Code–specific substitutions:

SKILL.md tool Claude Code equivalent
vscode_askQuestions Ask the user directly in the conversation
manage_todo_list Use task tracking internally
read_file Use Read tool
grep_search Use Grep tool

Steps (summary)

  1. Pre-flight — get_minimal_context(...) to confirm code-graph availability; check openspec/changes/ for in-progress OpenSpecs; read AGENTS.md § Hard rules and .github/copilot-instructions.md (when AGENTS.md has no Hard rules section, .github/copilot-instructions.md holds them all) if not already loaded.
  2. Parse the ticket — extract title, requirements, acceptance criteria, linked references. Flag vagueness.
  3. Investigate — use code-graph first (HARD RULE); identify affected files, existing patterns, risks, integration points. Scope investigation to the ticket.
  4. Flow into /coograph-plan or the coograph-propose skill — do NOT implement. The proposal skill creates artifacts and waits for explicit user approval.

Guardrails

  • Never skip pre-flight (especially the code-graph check).
  • Never start writing code before the OpenSpec is approved.
  • If the ticket is vague, ask focused clarifying questions one at a time before proposing.
  • If an overlapping in-progress OpenSpec exists, stop and ask whether to continue it or start fresh.

$ARGUMENTS

Models

Read the models block in openspec/config.yaml before delegating. When mode is preset or per-task, pass that agent's model on the Agent call; when it is off or unset, pass nothing and let the agent inherit the session model.

End your report with one line naming what ran where, so the setting is visible without reading config:

Read the full file on GitHub · 42 lines

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.

  1. 1mo ago Changed 19b298e5bfc7
  2. 1mo ago Changed · +15 lines e53c3d1bb158
  3. 2mo ago First seen · 27 lines · 0 tokens per session scan A 324030d8411f

Subscribe to this mod's changes

coograph-new-ticket is a command published in the GitHub repository paullukic/coograph (17 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 509 tokens. 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.

Related

coograph-new-ticket compared with commands from other repositories

coograph-new-ticket next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
coograph-new-ticketpaullukic/coographCommand1712d agoMITA0Claude Code
pull-repostravisjneuman/.claudeCommand107yesterdayMITA13Claude Code
security-scantravisjneuman/.claudeCommand107yesterdayMITA6Claude Code
test-suitetravisjneuman/.claudeCommand107yesterdayMITA7Claude Code
standardize-claude-mdtravisjneuman/.claudeCommand107yesterdayMITA18Claude Code
helptravisjneuman/.claudeCommand107yesterdayMITA9Claude Code
api-genhalflength-ampleness75/claude-code-recipesCommand223d agoMITA14Claude Code