spec-to-tickets

spec-to-tickets is a skill for Claude Code, Codex from me-cedric/agent-compass. It costs 75 tokens per session (1,106 once invoked), scanned A, original, no licence file.

A way to turn one section of a specification—the document describing required behaviour—into tracker-ticket text.

In plain words
What is it for?
It drafts a summary, a short reason, acceptance criteria, and a link back to the relevant specification section.
Why use it?
It reduces the work of writing tickets and keeps their acceptance checks tied to the original requirement.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit It drafts a summary, a short reason, acceptance criteria, and a link back to the relevant specification section.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/me-cedric/agent-compass/spec-to-tickets
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add me-cedric/agent-compass --skill spec-to-tickets
Clone the repo
git clone --depth 1 https://github.com/me-cedric/agent-compass

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.

agentmods badge for spec-to-tickets

README.md
[![agentmods](https://agentmods.dev/badge/skills/me-cedric/agent-compass/spec-to-tickets/github.svg)](https://agentmods.dev/skills/me-cedric/agent-compass/spec-to-tickets)
Your own site
<a href="https://agentmods.dev/skills/me-cedric/agent-compass/spec-to-tickets"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/spec-to-tickets/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 spec-to-tickets

Your own site · 80×15
<a href="https://agentmods.dev/skills/me-cedric/agent-compass/spec-to-tickets"><img src="https://agentmods.dev/badge/skills/me-cedric/agent-compass/spec-to-tickets.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,106 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 unknown 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.00075 $0.01106
Opus 5 $0.00037 $0.00553
Sonnet 5 $0.00015 $0.00221
Haiku 4.5 $0.00007 $0.00111

Measured 10d ago against content hash b8a7e2c21ca6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

spec-to-tickets 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.

skills/spec-to-tickets/SKILL.md · 121 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

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. 10d ago First seen · 121 lines · 75 tokens per session scan A b8a7e2c21ca6

Subscribe to this mod's changes

spec-to-tickets is a skill published in the GitHub repository me-cedric/agent-compass (2 stars, last pushed 10d ago), with no licence file. It adds 75 tokens to every session and 1,106 once invoked, about $0.0004 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-31.

Related

Other skills, from other repositories

todo-tracker

Persistent TODO scratch pad for tracking tasks across sessions. Use when the user asks to add, list, complete, remove, or summarize tasks in a portable workspace Markdown file. Uses stable task IDs and exact matching; heartbeat reporting is opt-in and count-only.

jdrhyne/agent-skills · 55 tokens

prd

A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.

Insajin/autopus-adk · 11 tokens

product-discovery

Product discovery workflow with OST, assumption testing, and interview scripts.

Insajin/autopus-adk · 16 tokens

team-coordination

Inspired by the Disp8chTeam multi-agent coordination framework — enables you to organize AI agents into collaborative crews with workspace isolation, P2P messaging, and dependency-aware task management.

aaronnat23/disp8ch · 0 tokens

jira

Read, search, draft, create, or update Jira work. Use only with explicit Jira or Atlassian context, a Jira URL, or a Jira-style issue key such as PROJ-123; generic mentions of an issue, ticket, sprint, or backlog are not sufficient.

jdrhyne/agent-skills · 59 tokens

planner

Interactive planning and execution for complex tasks. Use when breaking down multi-step projects (planning) or executing approved plans through delegation (execution). Planning creates milestones with specifications; execution delegates to specialized agents. Use when you say "plan this feature", "create…

rjmurillo/ai-agents · 60 tokens