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.
curl -O https://raw.githubusercontent.com/paullukic/coograph/main/.github/skills/coograph-new-ticket/SKILL.mdgit clone --depth 1 https://github.com/paullukic/coographWrote 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/paullukic/coograph/coograph-new-ticket)<a href="https://agentmods.dev/skills/paullukic/coograph/coograph-new-ticket"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/paullukic/coograph/coograph-new-ticket"><img src="https://agentmods.dev/badge/skills/paullukic/coograph/coograph-new-ticket.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.00044 | $0.00615 |
| Opus 5 | $0.00022 | $0.00308 |
| Sonnet 5 | $0.00009 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
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 11d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start work on a new ticket — run pre-flight, investigate, and propose a change.
Step 1: Pre-flight checks
Before doing anything else:
- Code-graph availability — call
get_minimal_contextwith a one-line summary of the ticket. Record whether code-graph is available. If available, use it for ALL navigation in subsequent steps. - Check for in-progress work — list
openspec/changes/(skiparchive/). If an existing OpenSpec overlaps with this ticket, stop and ask: "There's an in-progress change<name>— is this ticket related, or should I start fresh?" - Read conventions — read
.github/copilot-instructions.mdif not already loaded.
Step 2: Parse the ticket
Extract from the user's input:
- Title/summary — one-line description
- Requirements — what needs to be built or changed
- Acceptance criteria — if provided
- Linked references — URLs, ticket IDs, file paths mentioned
If the ticket is vague (no specific files, unclear deliverable, touches 3+ areas), note this — it affects Step 3.
Step 3: Investigate the codebase
Use code-graph tools (or fallback chain) to:
- Identify files and modules affected by the ticket
- Read relevant source code to understand current behavior
- Find existing patterns the implementation should follow
- Surface risks, dependencies, and integration points
Scope the investigation to the ticket. Don't audit the entire codebase.
If the ticket is vague or complex (identified in Step 2):
- Run deeper investigation
- Ask the user focused clarifying questions (one at a time, with choices when possible)
- Do NOT proceed to Step 4 until requirements are clear
If the ticket is specific and well-scoped:
- Investigation can be brief
- Proceed directly to Step 4
Step 4: Flow into OpenSpec proposal
Once investigation is complete and requirements are clear, invoke the coograph-propose skill to create the proposal.
Pass it a clear description synthesized from the ticket + your investigation findings.
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.
- 11d ago First seen · 67 lines · 44 tokens per session scan A f7c3246237cd
coograph-new-ticket is a skill published in the GitHub repository paullukic/coograph (17 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 615 once invoked, about $0.0002 per session on Opus 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
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
innovation
Innovation management expertise for innovation frameworks (Design Thinking, Stage-Gate), ideation processes, innovation portfolio management, venture capital, open innovation, and IP strategy. Use when driving innovation, managing R&D portfolios, or building innovation programs.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.